Chapter 7 Resources
Resources represent inputs and outputs, the “things” that are produced, modified, consumed, or in any way used by Nodes. A more thorough description was provided in Section 3.8, “ResourcePool and its Resource Children”. The Resources in this chapter are divided into two sections. The first section documents all of the Resources of Class Intent . The second section documents the rest of the Resources that have been defined for JDF.
7.1 Intent Resources
As was described in Section 4.1.1, “Product Intent Constructs”, Intent Resource s are designed to narrow down the available options when defining a JDF Job. Many of the Elements in Intent Resource s are optional . If an optional Element of an Intent Resource is omitted and no additional information is specified in the description, the value defaults to “don’t care”. If an entire Intent Resource that specifies a given product feature is omitted, then that feature is not requested. For instance, if a Product Intent Node has no ResourceLink to NumberingIntent , then no numbering is requested. The characteristics of the product that are not specified through the use of Intent Resource s will be selected by the system that Processes the Intent Resource s. The system that processes the Product Intent data in a JDF Job ticket may insert the details of its selection into the JDF data for the Job. See Section 1.4.2.1, “Conformance Requirements for Support of Attributes and Attribute Values” for more information on the handling and processing of systems-specified default values.
All Intent Resource s share a set of Subelements that allow a Request for Quote to describe a range of acceptable values for various aspects of the product. These elements, taken together, allow an administrator to provide a specific value for the quote. The section below (Section 7.1.1, “Span Subelements of an Intent Resource”) describes these Elements.
Each of the following sections begins with a brief narrative description of the Resource. Following that is a list containing details about the properties of the Resource, as shown below. The first item in the list provides the Class of the Resource, which, in this section is always Intent . For more information on Resource Class, see Section 3.8.5, “Resource Classes”. A template of this list is shown below.
After the list describing the Resource properties, each section contains tables that outline the structure of each Resource and, when applicable, the abstract or Subelement information that pertains to the Resource structure. The first column contains the name of the Attribute or Element. A template of these tables is also provided below.
Note: for the Resource Properties Template below, the italicized text describes the actual text that would be in its place in an actual Resource definition.
Note also: for the Resource Structure Template table below: Cardinality in the Name column of the Resource Structure Template table refers to a cardinality symbol, which is either empty or consists of a symbol, such as “?”. Examples described by the Name column include: “ Ink *” and “ FileSpec ( DeviceLinkProfile ) ? ”. For further details, see Section 1.3.4, “Specification of Cardinality”.
List of parent Resources that may contain Elements of this type.
List of Process Resources to which an Intent Resource is generally identified with. In practice, the Process Resources will contain the data with which the customer’s intent is fulfilled in production and distribution of the product. This is a list of the primary Resources and not a complete list.
List of recommended Partition Keys: For a complete list of Partition Keys, see the description of PartIDKeys in Table 3-27, “Partitionable Resource Element”. Note that Resources may be Partitioned by keys that are not specified in this list.
List of JDF Node types that use the Resource as an Input Resource.
List of JDF Node types that create the Resource as an Output Resource.
|
Information about the Element. Note: the “element” data type means that the specified Element must be an in-line Subelement within the Resource. |
||
|
Note: the “refelement” data type means that the specified Element is based on other atomic Resources or Resource Elements. The specified Element must be either an in-line Element or an instance of a ResourceRef Element (see Section 3.10.2, “ResourceRef - Element for Inter-Resource Linking and refelement”). In case of a ResourceRef Element, a “Ref” must be appended to the name specified in the table column entitled “Name”. |
7.1.1 Span Subelements of an Intent Resource
Intent Resource s contain Subelements that allow spans of values to be specified. These Subelements also provide mechanisms to select a set of values from the provided range and map them to a set of quotes. These Subelements are called Span Elements. The Span Element to use is determined by the data type of the values to be recorded. Span Elements are defined to facilitate negotiation between buyer and provider as defined in Section 4.1.2, “Defining Business Objects Using Intent Resources”.
7.1.1.1 Abstract Span Element
Span Elements of Intent Resource s have a common set of Attributes that define the priority, data type and requested identity of the Element. These common Attributes are described in Table 7-2, “Abstract Span Element”. In addition, Abstract Span Elements have at least four Attributes that define the data type dependent aspects of the span. The data type of these values depends on the data type of the span and is defined in the following sections:
Actual -The intended value agreed to by the producer of the product.
OfferRange - A proposed range of equivalent values in cost that are defined by the producer of the product.
Preferred - A preferred value defined by the recipient of the product.
Range - A proposed range of values defined by the recipient of the product.
|
Describes the data type of the Span Element within an Intent Resource . This Attribute is provided for applications that do not have access to schema validation. |
|||
|
Indicates the importance of the specific intent. Suggested - The customer will accept a value of Actual that is different than the value of Preferred or outside of Range . Required - The customer expects the Actual to be equal to Preferred or within Range . Note that the Attribute Preferred is available in the data types which inherit from this Abstract type. Deprecation note: starting with JDF 1.2, use SettingsPolicy . |
|||
7.1.1.2 Span Elements
The Data Type column of tables for Intent Resource s (below) can contain the same data types as non- Intent Resource s (namely data types defined in the Section 1.5, “Data Structures” ) as well as Span Elements that are listed in the Table 7-3, “List of Span Elements”. In Intent Resource tables, XXXSpan Elements are treated as Attribute-like data types even though Span Elements are technically XML elements because the semantic usage of the Span Elements is equivalent to the usage of Attributes in Process Resources.
Each Span Element contains Attributes or Subelements listed in Table 7-2, “Abstract Span Element” and in the pertinent Span Element listed in Table 7-3, “List of Span Elements”.
|
Describes an intent in which the principal information is that a specific option is requested. |
||
7.1.1.2.1 DurationSpan
This Span Subelement is used to describe a selection of instances in time. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element”.
7.1.1.2.2 EnumerationSpan
This Span Subelement is used to describe ranges of enumerative values. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element”. It is identical to the NameSpan Element except for the fact that it describes a closed list of enumeration values.
Example 7-1: EnumerationSpan
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="Product" JobPartID="ID300" Version="1.4">
<BindingIntent Class="Intent" ID="BI1" Status="Available">
<BindingType DataType="EnumerationSpan" Actual="Ring"/>
< HoleType DataType = "EnumerationSpan" Range = "R4m-DIN-A5 R6m-DIN-A5" >
< Comment Name = "R4m-DIN-A5" >
4 equidistant holes on each side of a hexagonal piece of paper
< Comment Name = "R6m-DIN-A5" >
6 equidistant holes on each side of a hexagonal piece of paper
<Component Class="Quantity" ID="cI1" Status="Unavailable"
<BindingIntentLink Usage="Input" rRef="BI1"/>
<ComponentLink Usage="Output" rRef="cI1"/>
7.1.1.2.3 IntegerSpan
This Span Subelement is used to describe ranges of integer values. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element”.
7.1.1.2.4 NameSpan
This Span Subelement is used to describe name ranges. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element” . It is identical to the EnumerationSpan Element except for the fact that it describes an extensible list of NMTOKEN values.
7.1.1.2.5 NumberSpan
This Span Subelement is used to describe a numerical range of values. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element”.
7.1.1.2.6 OptionSpan
This Span Subelement is used to describe a range of options or Boolean values. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element”.
7.1.1.2.7 ShapeSpan
This Span Subelement is used to describe ranges of numerical value pairs. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element”.
7.1.1.2.8 StringSpan
This Span Subelement is used to describe string ranges. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element” .
7.1.1.2.9 TimeSpan
This Span Subelement is used to describe a selection of instances in time. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element”.
7.1.1.2.10 XYPairSpan
This Span Subelement is used to describe ranges of numerical value pairs. It inherits from the Abstract Span Element described in Section 7.1.1.1, “Abstract Span Element”.
7.1.2 ArtDeliveryIntent
This Resource specifies the prepress art delivery intent for a JDF Job and maps the items to the appropriate Reader Pages and separations. Art delivery refers to any physical or electronic asset that is needed for processing the Job.
DeliveryParams , DigitalDeliveryParams
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Specifies the latest time by which the transfer of the artwork will be made. |
||
|
Specifies the latest time by which the transfer will be made relative to the date of the purchase order. Within an RFQ or a Quote, at most one of either ArtDeliveryDate or ArtDeliveryDuration must be specified. Within a purchase order, only ArtDeliveryDate is allowed. |
||
|
Describes what is to happen to the artwork after usage. The address for the Return and Pickup values must be specified by a Contact [contains (@ ContactTypes , "ArtReturn" )]/ Address . ReturnWithProof - The artwork is delivered back to the customer together with the proof if there is any. ReturnWithProduct - The artwork is delivered back to the customer together with the final product. Return - The artwork is delivered back independently directly after usage. Pickup - The customer picks up the artwork. Destroy - The printer destroys the artwork. PrinterOwns - The artwork belongs to the printer. Store - The printer has to store the artwork for future purposes. |
||
|
Specifies who pays for a delivery being made by a third party. Values are from : DeliveryIntent / DeliveryCharge . |
||
|
Specifies the delivery method, which can be a generic method. Local - The files are already in place and a DigitalDelivery Process is not needed. New in JDF 1.3 NetworkCopy - This includes LAN and VPN. WebServer - Upload / download from HTTP / FTP server. UPS - a delivery service brand. DHL - a delivery service brand. FedEx - a delivery service brand. |
||
|
Information about a Preflight Process probably applied to the artworks before being submitted. NotPerformed - No preflighting was applied. WithErrors - Preflighting resulted in error messages and possibly warning messages. WithWarnings - Preflighting resulted in warning messages and no errors. WithoutErrors - Preflighting was successful. No errors and no warnings occurred. |
||
|
Type of printer created intermediate materials that are to be sent to the customer after usage. DigitalMedia - Digital data on media, (e.g., a CD). DigitalNetwork - Digital data via network. ExposedPlate - Pre-exposed press plates, usually used for a rerun. ImposedFilm - Film of the imposed surfaces. LooseFilm - Film of individual pages or sections. OriginalPhysicalArt - Analog artwork, (e.g., reflective or transparencies). Tool - Tools needed for processing the Job, (e.g., a die for die cutting or embossing stamp). None - No intermediate materials are to be returned to the customer. |
||
|
Specifies a delivery method for returning the artwork if ArtHandling/@ Actual = "Return" and for the printer created materials listed in ReturnList . |
||
|
Describes the responsibility of the transfer. BuyerToPrinterDeliver - The buyer delivers the artwork to the printer. The printer may specify in the quote a special Contact [contains (@ ContactTypes , "Delivery" )] to specify where the buyer is to send the artwork. BuyerToPrinterPickup - The printer picks up the artwork. The Contact [contains (@ ContactTypes , "Pickup" )] specifies where the printer has to pick up the artwork. |
||
|
Company ? |
Address and further information of the art delivery. Company must not be specified unless the printer is expected to pick up the art delivery at this address. In JDF 1.1 and beyond, Company is a Subelement of Contact . |
|
|
Contact * |
Address and further information about the transfer of the artwork. The actual delivery address
must
be specified by
The actual pickup address
must
be specified by |
7.1.2.1 Element: ArtDelivery
Each ArtDelivery Element defines a set of existing products that are needed to create the specified product. Attributes that are specified in an ArtDelivery Element overwrite those that are specified in their parent ArtDeliveryIntent Element. If optional Attributes are not specified, their values default to the values specified in ArtDeliveryIntent .
|
Number of physical objects to be delivered. Only valid if no detailed Resource description (e.g., ExposedMedia , RunList , ScanParams , DigitalMedia or Tool ) is specified. |
||
|
Specifies the latest time by which the transfer of the artwork will be made. |
||
|
Specifies the latest time by which the transfer will be made relative to the date of the purchase order. Within an RFQ or a Quote, at most one of either ArtDeliveryDate or ArtDeliveryDuration must be specified. Within a purchase order, only the ArtDeliveryDate is allowed. |
||
|
DigitalFile - Digital data irrespective of the delivery mechanism. The union of "DigitalMedia" and "DigitalNetwork" . New in JDF 1.2 DigitalMedia - Digital data on media, (e.g., a CD). DigitalNetwork - Digital data via network. ExposedPlate - Pre-exposed press plates, usually used for a rerun. ImposedFilm - Film of the imposed surfaces. LooseFilm - Film of individual pages or sections. OriginalPhysicalArt - Analog artwork, (e.g., reflective or transparencies). Proof - Physical proof delivered with digital scan or separated film asset. Tool - Tools needed for processing the Job, (e.g., a die for die cutting or embossing stamp). |
||
|
Describes what is to happen to the artwork after usage. The address for the "Return" and "Pickup" values must be specified by Contact [contains (@ ContactTypes , "ArtReturn" )]/ Address . Default value is from: ArtDeliveryIntent / ArtHandling . ReturnWithProof - The artwork is delivered back to the customer together with the proof if there is any. ReturnWithProduct - The artwork is delivered back to the customer together with the final product. Return - The artwork is delivered back independently directly after usage. Pickup - The customer picks up the artwork. Destroy - The printer destroys the artwork. PrinterOwns - The artwork belongs to the printer. Store - The printer has to store the artwork for future purposes. |
||
|
Specifies who pays for a delivery being made by a third party. Default value is from: ArtDeliveryIntent / DeliveryCharge . Values are from : DeliveryIntent / DeliveryCharge . |
||
|
Specifies a delivery method. It may be a generic item from the list defined in Method in ArtDeliveryIntent . Values include those from: ArtDeliveryIntent / Method |
||
|
Set of pages of the output Component that are filled by this ArtDelivery . This maps the pages in the ArtDelivery to the Pages in the product that is produced. For example if PageList = "3 ~ 5" , page 0 of the ArtDelivery (e.g., RunList ) is page 3 in the product, page 1 is page 4, etc. If not specified, the PageList must include all pages in reader order. The indices specified in PageList reference the PageData Elements defined in PageList . |
||
|
Pointer to the output information created by the preflight tool if PreflightStatus is either "WithoutErrors" or "WithErrors" . |
||
|
Information about a Preflight Process. Default value is from: ArtDeliveryIntent /@ PreflightStatus . Values are from : ArtDeliveryIntent /@ PreflightStatus . |
||
|
Specifies a delivery method for returning the artwork if ArtHandling/@Actual = "Return" . Default value is from: ArtDeliveryIntent / ReturnMethod . Values include those from: ArtDeliveryIntent / ReturnMethod |
||
|
The service level of the specific carrier. Default value is from: ArtDeliveryIntent / ServiceLevel . Values include those from: ArtDeliveryIntent / ServiceLevel |
||
|
Describes the responsibility of the transfer. Default value is from: ArtDeliveryIntent / Transfer . Values are from : ArtDeliveryIntent / Transfer . |
||
|
Company ? |
Address and further information about the art delivery. This must not be specified unless the printer is expected to pick up the art delivery at this address. In JDF 1.1 and beyond, Company is a Subelement of Contact . |
|
|
Description of a physical component, (e.g., physical artwork). If neither Component , ExposedMedia , nor RunList are specified, no details of the ArtDelivery except the ArtDeliveryType and Amount are known. |
||
|
Contact * |
Address and further information about the art transfer. Default value is from: ArtDeliveryIntent / Contact . |
|
|
Description of any digital media, (e.g., CD or tape with artwork that will be delivered). If neither ExposedMedia , RunList , DigitalMedia , nor Tool are specified, no details of the ArtDelivery except the ArtDeliveryType and Amount are known. |
||
|
Description of exposed media, (e.g., film, plate or proof). If neither ExposedMedia , RunList , DigitalMedia , nor Tool are specified, no details of the ArtDelivery , except the ArtDeliveryType and Amount , are known. |
||
|
RunList ? |
Link to digital artwork that is accessible via a set of URLs that are defined in the RunList / LayoutElement / FileSpec /@ URL . If neither DigitalMedia , ExposedMedia , RunList , nor Tool are specified, no details of the ArtDelivery except the ArtDeliveryType and Amount are known. |
|
|
Description of a ScanParams that defines scanning details for the exposed media defined by ExposedMedia . |
||
|
Tool ? |
Details of the Tool if ArtDeliveryType = "Tool" . If neither ExposedMedia , RunList , DigitalMedia , nor Tool are specified, no details of the ArtDelivery except the ArtDeliveryType and Amount are known. |
7.1.3 BindingIntent
This Resource specifies the binding intent for a JDF Job using information that identifies the desired type of binding and which side is to be bound. The input components that are used as a cover must have a ProcessUsage of Cover . The input components that are used as a hard cover jacket must have a ProcessUsage of Jacket . The input components that are used as a end Sheets for hardcover or soft cover binding must have a ProcessUsage of EndSheet . All other input components are bound in the order of their appearance in the ResourceLinkPool of the JDF Node that contains the BindingIntent .
BlockPreparationParams , CaseMakingParams , CasingInParams , ChannelBindingParams , CoilBindingParams , CoverApplicationParams , EndSheetGluingParams , GlueApplication , GluingParams , GlueLine , InsertingParams , JacketingParams , PlasticCombBindingParams , RingBindingParams , SaddleStitchingParams , SpinePreparationParams , SpineTapingParams , StitchingParams , StripBindingParams , ThreadSealingParams , ThreadSewingParams , WireCombBindingParams
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Defines the color of the back cover material of the binding. Default value is from: @ CoverColor Values are from : Table A-3, “NamedColor Enumeration Values”. |
||
|
A more specific, specialized or site-defined name for the color. If BackCoverColorDetails is supplied, BackCoverColor SHOULD also be supplied. |
||
|
Defines the color of the spine material of the binding. Values are from : Table A-3, “NamedColor Enumeration Values”. |
||
|
A more specific, specialized or site-defined name for the color. If BindingColorDetails is supplied, BindingColor SHOULD also be supplied. |
||
|
Indicates which side is to be bound when no content. Thus, no orientation is available, but a quote for binding is needed. |
||
|
Specifies whether the child Component Resources are to be collected or gathered if multiple child Component Resources are combined. None - The child Component Resource are NOT bound together. Typically used for flatwork Jobs. New in JDF 1.4 Collecting - The child Component Resources are collected on a spine and placed within one another. The first Component is on the outside. Gathering - The child Component Resources are gathered on a pile and placed on top of one another. The first Component is on the top. List - More complex ordering of child Component Resources is specified using the BindList in this Intent Resource for this product. |
||
|
Indicates which side are to be bound. Each of these values is intended to identify an edge of the Job. These edges are defined relative to the orientation of the first page in the Job with content on it. Constraint: If both BindingSide and BindingLength are specified, BindingSide has precedence Default value is from: BindingLength , unless a non-empty BindList was specified. |
||
|
Describes the desired binding for the Job. Values are from : Table 7-17, “BindingType Attribute Values”. |
||
|
Defines the color of the cover material of the binding. Values are from : Table A-3, “NamedColor Enumeration Values”. |
||
|
A more specific, specialized or site-defined name for the color. If CoverColorDetails is supplied, CoverColor SHOULD also be supplied. |
||
|
Details of AdhesiveBinding . Replaced with SoftCoverBinding in JDF 1.1. |
||
|
BindList ? |
Details of binding of individual child Component Resources. |
|
|
BookCase ? |
Details of the Book Case. Used in Combination with AdhesiveBinding , ThreadSewing or ThreadSealing . Replaced with HardCoverBinding in JDF 1.1. |
|
|
Details of ChannelBinding . |
||
|
Details of CoilBinding . |
||
|
Details of EdgeGluing . |
||
|
Details of HardCoverBinding . |
||
|
Details of PlasticCombBinding . |
||
|
Details of RingBinding . |
||
|
Details of SaddleStitching . |
||
|
Details of SideSewing . |
||
|
Details of SideStitching . |
||
|
Details of SoftCoverBinding . |
||
|
Details of StripBinding . |
||
|
Tabs ? |
Details of Tabs . |
|
|
Tape ? |
Details of Tape binding. |
|
|
Details of ThreadSealing . |
||
|
Details of ThreadSewing . |
||
|
Details of VeloBinding . Renamed to StripBinding in JDF 1.1. |
||
|
Details of WireCombBinding . |
-- Attribute: BindingType
|
This type of binding can be handled with the AdhesiveBinding Process. It includes perfect binding. Deprecated in JDF 1.1 and replaced with SoftCover or HardCover . |
|
|
This type of binding can be handled with the ChannelBinding Process. |
|
|
This type of binding can be handled with the CoilBinding Process. |
|
|
Stitch in the corner that is at the clockwise end binding edge. For example, to stitch in the top left corner, set BindingSide /@ Actual = "Left" . This type of binding can be handled with the Stitching Process. |
|
|
Gluing gathered Sheets at one edge of the pile. This Type of Binding can be handled with the Gluing Process. Products of this type are also referred to as padded. |
|
|
This type of binding defines a stack of pages with no additional binding. |
|
|
This type of binding can be handled with the PlasticCombBinding Process. |
|
|
This type of binding can be handled with the RingBinding Process. |
|
|
This type of binding can be handled with the Stitching Process. |
|
|
This type of binding can be handled with the ThreadSewing Process. |
|
|
This type of binding can be handled with the ThreadSewing Process. |
|
|
This type of binding can be handled with the Stitching Process. |
|
|
This type of binding defines a soft cover bound book. It includes perfect binding. |
|
|
This type of binding can be handled with the StripBinding Process. |
|
|
This type of binding is an inexpensive version of the SoftCover . |
|
|
This type of binding can be handled with the ThreadSealing Process. |
|
|
This type of binding can be handled with the WireCombBinding Process. |
7.1.3.1 Element: BindList
BindList is used to describe complex bindings where more than one child is bound into a cover, e.g., in promotional products.
|
BindItem * |
7.1.3.2 Element: BindItem
A child BindItem is bound to a parent item. The position of the spine of the child BindItem is defined by ChildFolio and the position of the child BindItem in the parent is defined by ParentFolio .
|
Describes the desired binding for the individual BindItem . Default value is from: BindingIntent / BindingType . Values are from : BindingIntent / BindingType . |
||
|
Definition of the fold between two pages in the BindItem component that is bound to the cover. The two numbers (as integers) in the ChildFolio Attribute are the page numbers of the two outer pages of the child Component which touch the cover or another parent Component . The pages are counted in the order as described in LayoutIntent /@ FolioCount of the child product. Defaults to the spine of the child. |
||
|
Definition of the fold between two pages in the Cover Component that receive the BindItem . The two numbers (as integers) in the ParentFolio Attribute are the page numbers in the Cover Component which touch the child Component . The pages are counted in the order as described in LayoutIntent /@ FolioCount of the cover product. |
||
|
Rotation and offset between the Component to be inserted and the parent Component . For details on transformations, see Section 2.5.2, “Coordinates and Transformations”. |
||
|
List of pages of the Cover that wrap around a BindItem after all folds are correctly positioned. It is sufficient to specify the pages of the Front surface of the cover. Note that this key must not be specified unless the folding is ambiguous. |
||
|
Details of ChannelBinding . |
||
|
Details of CoilBinding . |
||
|
Details of EdgeGluing . |
||
|
Details of HardCoverBinding . |
||
|
Details of PlasticCombBinding . |
||
|
Details of RingBinding . |
||
|
Details of SaddleStitching . |
||
|
Details of SideSewing . |
||
|
Details of SideStitching . |
||
|
Details of SoftCoverBinding . |
||
|
Details of StripBinding . |
||
|
Tabs ? |
Details of Tabs . |
|
|
Tape ? |
Details of Tape binding. |
|
|
Details of ThreadSealing . |
||
|
Details of ThreadSewing . |
||
|
Details of WireCombBinding . |
7.1.3.3 Element: AdhesiveBinding
The table defining the deprecated AdhesiveBinding Subelement has been moved to Section P.4.1, “BindingIntent Deprecated Subelements” .
7.1.3.4 Element: BookCase
The table defining the deprecated BookCase Subelement has been moved to Section P.4.1, “BindingIntent Deprecated Subelements” .
7.1.3.5 Element: ChannelBinding
|
Strings providing available brand names for the ChannelBinding . |
||
|
If "true" , the clamp used in ChannelBinding includes a preassembled cover. |
||
|
Specifies thickness of board which is wrapped as front and back covers of a case bound book, in points. |
7.1.3.6 Element: CoilBinding
|
The coil materials available for CoilBinding . |
||
|
HoleList ? |
7.1.3.7 Element: EdgeGluing
7.1.3.8 Element: HardCoverBinding
|
Defines the style of the cover board. Simple - Single layer cover board, see Figure 7-1. Padded - Padded cover board, see Figure 7-2. |
||
|
Specified if end Sheets are applied. Additional details of the EndSheets may be specified by supplying an input Component with ProcessUsage = "EndSheet" . |
||
|
The following case binding choice specifies the use of headbands on a case bound book. If "true" , headbands are inserted both top and bottom. |
||
|
Defines the color of the headband. Values are from : Table A-3, “NamedColor Enumeration Values”. |
||
|
A more specific, specialized or site-defined name for the color. If HeadBandColorDetails is supplied, HeadBandColor SHOULD also be supplied. |
||
|
Specifies whether a hard cover jacket is needed and how it is attached. Details of the jacket may be described in the Component with ProcessUsage = "Jacket". |
||
|
Dimension of the jacket folds. See JacketingParams for details. |
||
|
Bind the book block at the open edge, so that the folds are visible on the outside. If not specified, explicitly, this option is never selected. |
||
|
Brushing option for SpinePreparation . |
||
|
Fiber roughing option for SpinePreparation . |
||
|
Leveling option for SpinePreparation . |
||
|
Milling option for SpinePreparation . |
||
|
Notching option for SpinePreparation . |
||
|
Sanding option for SpinePreparation . |
||
|
Shredding option for SpinePreparation . |
||
|
Specifies thickness of board which is wrapped as front and back covers of a case bound book, in points. |
||
|
|
7.1.3.9 Element: PlasticCombBinding
|
Strings providing available brand names for the plastic comb. |
||
|
The distance between the “teeth” in PlasticCombBinding and the distance between the holes of the prepunched leaves must be the same. The following values from the hole type catalog in Appendix L, “JDF/CIP4 Hole Pattern Catalog” exist: P12m-rect-02 - Distance = 12 mm; Holes = 7 mm x 3 mm P16_9i-rect-0t - Distance = 14.28 mm; Holes = 8 mm x 3 mm Euro - Distance = 12 mm; Holes = 7 mm x 3 mm Deprecated in JDF 1.1 USA1 - Distance = 14.28 mm; Holes = 8 mm x 3 mm. Deprecated in JDF 1.1 |
||
|
HoleList ? |
Details of the holes for the plastic comb. Note that Shape is always rectangular by design of the plastic combs. |
7.1.3.10 Element: RingBinding
|
Strings providing available brand names for RingBinding . |
||
|
The following describe RingBinding binder materials used. Cardboard - Cardboard with no covering. ClothCovered - Cardboard with cloth covering. Plastic - Binder cover fabricated from solid plastic Sheet material, (e.g., PVC Sheet). |
||
|
Predefined hole pattern for the ring system. Multiple hole patterns are not allowed, (e.g., 3-hole ring binding and 4-hole ring binding holes on one piece of media). For details of the hole types, see the values. Values are from : Appendix L, “JDF/CIP4 Hole Pattern Catalog” . |
||
|
Size of the rings in points. The value used in production must be suitable for specified values of HoleType . Note that in ring shapes other than round, this size is specified by industry-standard method. |
||
|
The ring binder used includes a lever for opening and closing. |
||
|
RingBinding shapes. |
||
|
The following RingBinding choice describes mounting of the ring mechanism in binder case. If "true" , the heads of the rivets are visible on the exterior of the binder. If "false" , the binder covering material covers the rivet heads. |
||
|
The values are RingBinding clear vinyl outer wrap types and are used on top of a colored base wrap. Embedded - Printed material is embedded by sealing between the colored and clear vinyl layers during binder manufacturing. Pocket - Binder is designed so that printed material can be inserted between the color and clear vinyl layers after binder manufacturing. |
7.1.3.12 Element: SideSewing
This is a placeholder that might be filled with private or future data.
7.1.3.14 Element: SoftCoverBinding
|
Specified if end Sheets are applied. Additional details of the EndSheets may be specified by supplying an input Component with ProcessUsage = "EndSheet" . |
||
|
Definition of the dimension of the folding width of the front cover fold. See JacketingParams for details. |
||
|
Definition of the dimension of the folding width of the back cover fold. If not specified, FoldingWidthBack defaults to FoldingWidth . |
||
|
Glue procedure used to glue the book block to the cover. SideOnly - Glued at the side or endsheets but not at the spine. SideOnly books are also referred to as “layflat” if EndSheets are also specified. See Figure 7-3, “Structure of a book with GlueProcedure = "SideOnly" (Layflat)” . |
||
|
Scoring option for SoftCoverBinding . Values are based on viewing the cover in its flat, prebound state. |
||
|
Brushing option for SpinePreparation . |
||
|
FiberRoughing option for SpinePreparation . |
||
|
Leveling option for SpinePreparation . |
||
|
Milling option for SpinePreparation . |
||
|
Notching option for SpinePreparation . |
||
|
Sanding option for SpinePreparation . |
||
|
Shredding option for SpinePreparation . |
|
7.1.3.15 Element: StripBinding
|
HoleList ? |
Note that Shape is always round by design of the strip poles. |
7.1.3.16 Element: Tabs
Specifies tabs in a bound document.
|
Number of rows of tabs on the face of the book. Deprecation note: starting with JDF 1.4, TabBanks should be calculated from TabCount and TabsPerBank . |
||
|
Strings providing available brand names for the Tabs . |
||
|
Number of tabs across all banks. If TabsPerSet is not an even multiple of TabsPerBank , the last bank in each set is partially filled. |
||
|
Number of equal-sized tabs in a single bank if all positions were filled. Note that banks can have tabs only in some of the possible positions |
||
|
Distance tab extends beyond the body of the book block, in points. |
||
|
If "true" , Color will be applied not only on tab extension, but also on tab body. Note that lack of body copy allows all tabs within a bank to be printed on a single Sheet. |
||
|
Specifies the color of the mylar used to reinforce the tab extension. This is conditional on TabExtensionMylar being "true" . Values are from : NamedColor (Section A.3.3.3, “NamedColor”). |
||
|
A more specific, specialized or site-defined name for the color. If TabMylarColorDetails is supplied, TabMylarColor SHOULD also be supplied. |
7.1.3.17 Element: Tape
|
Defines the color of the tape material of the binding. Values are from: Table A-3, “NamedColor Enumeration Values”. Deprecation note: starting with JDF 1.4, use BindingIntent /@ BindingColor . |
7.1.3.18 Element: ThreadSealing
This is a placeholder that might be filled with private or future data.
7.1.3.19 Element: ThreadSewing
|
If "true" , thermo-sealing is needed in ThreadSewing . |
7.1.3.20 Element: WireCombBinding
|
Strings providing available brand names for the WireCombBinding . |
||
|
The material used for forming the WireCombBinding . |
||
|
The shape of the WireCombBinding . Single - Each “tooth” is made with one wire. Twin - The shape of each “tooth” is made with a double wire, (e.g., Wire-O ). |
||
|
HoleList ? |
7.1.4 ColorIntent
This Resource specifies the type of ink to be used. Typically, the parameters consist of a manufacturer name and additional identifying information. The Resource also specifies any coatings and colors to be used, including the process color model and any spot colors.
Color , ColorantControl , ColorCorrectionParams , ColorPool , ColorSpaceConversionParams
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Material usually applied to a full surface on press as a protective or gloss-enhancing layer over ink. Note: The individual strings within Coatings are of type NMTOKENS and may contain multiple entries from the list of values. Note: that spot coating is specified in ColorsUsed . |
||
|
The color process (i.e., printing condition) requested for the Job. ColorStandard does not imply values for ColorsUsed . For instance, if ColorStandard is CMYK , ColorsUsed must still contain the four process colors Cyan , Magenta , Yellow and Black . If both of ColorICCStandard and ColorStandard are specified, then ColorICCStandard defines the ICC specific details, whereas ColorStandard defines the generic color standard. Values include those from: Table 7-37, “ColorStandard Attribute Values”. |
||
|
ColorICCStandard can be used to identify a specific standard printing condition, by reference to Characterization Data registered with the ICC ( http://www.color.org/drsection1.html ). This printing condition reference corresponds to the OutputIntent characterization referencing capability in PDF/X. The syntax will be Reference Name as shown in the examples below. Reference Name is the standard reference string name used in both JDF and PDF/X, defined for each printing condition in the characterization registry on the ICC website. FOGRA11 - Registered by FOGRA pertaining to offset commercial and specialty printing according to [ISO12647-2:2004] , positive plates, paper type 1 (gloss-coated, above 70 g /m2) and paper type 2 (matte-coated, above 70 g /m2), screen frequency 60/cm. Appropriate for black-backing measurement. FOGRA15 - Registered by FOGRA pertaining to offset commercial and specialty printing according to [ISO12647-2:2004] , positive plates, paper type 1 (gloss-coated, above 70 g /m2) and paper type 2 (matte-coated, above 70 g /m2), screen frequency 60/cm. Appropriate for self-backing measurement. CGATS TR001 - pertaining to printing conditions that conform to ANSI CGATS.6, which addresses Publication printing in the US as defined by SWOP. Note: If both of ColorICCStandard or ColorsUsed are specified, the union of the two is specified. If both of ColorICCStandard and ColorStandard are specified, then ColorICCStandard defines the ICC specific details, whereas ColorStandard defines the generic color standard. |
||
|
Cumulative colorant coverage percentage. For example, a full Sheet of 100% deep black in CMYK has Coverage /@ Actual = "400" . Typical coverages based on one color plane are: |
||
|
Name of the manufacturer of the ink requested, (e.g., "ACMEInk" , "CIP4_Ink_Company" etc.). |
||
|
Additional details about the colors used. The ColorPool Resource may include some or all details about both ColorsUsed separation spot colors, spot colors contained in Job files that will be printed using process color equivalents and the ColorStandard process colors. |
||
|
Array of colorant separation names that are requested. If not specified, the values are implied from ColorStandard . If specified, ColorsUsed must contain a list of all separation names used by the Job. Note: If additional information about the colors and colorants is needed, it can be specified in the referenced ColorPool Resource. |
-- Attribute: ColorStandard
|
Flexographic Image Reproduction Specifications & Tolerances. |
|
|
General Requirements for Applications in Commercial Offset Lithography |
|
|
[ISO12647-2:2004] offset standard. |
|
|
Japan Color 2001 standard [japancolor] . |
|
|
Generic single color printing condition, (e.g., black and white or one single spot color). |
|
|
No marks. Used to define one-sided printing. Deprecation note: starting with JDF 1.2, use LayoutIntent /@ Sides instead.) |
|
|
Specifications for Web Offset Publications. Registered by ANSI with the ICC as ICC:CGATS TR001 pertaining to printing conditions that conform to ANSI CGATS.6 which is based on Publication printing in the US as defined by SWOP, Inc. |
7.1.4.1 Element: ColorsUsed
|
These can be process colors, generic spot colors or named spot colors. In addition, partial (spot) coating is specified by adding a SeparationSpec with anything from Coatings as SeparationSpec /@ Name : Spot - Generic spot color of which the details are unknown. Spot may be specified multiple times in one ColorsUsed Element. New in JDF 1.2 Varnish - Generic varnish including DullVarnish, GlossVarnish and SatinVarnish. New in JDF 1.3 |
7.1.5 DeliveryIntent
Summarizes the options that describe pickup or delivery time and location of the Physical Resource s of a Job. It also defines the number of copies that are requested for a specific Job or delivery. This includes delivery of both final products and of proofs. DeliveryIntent may also be used to describe the delivery of intermediate products such as partial products in a subcontracting description.
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
The quote that is specified by this DeliveryIntent has been accepted. Deprecation note: starting with JDF 1.3, contract negotiation information has been removed and will be handled by the business wrapper around JDF, e.g. PrintTalk. |
||
|
Number of components used to calculate the value of the AdditionalPrice Attribute in the Pricing . This value applies to the number of additional items in one DropIntent / DropItemIntent and not to the total additional number of items. In JDF 1.3 and beyond, pricing information has been removed and will be handled by the business wrapper around JDF, e.g. PrintTalk. |
||
|
Specifies who pays for a delivery being made by a third party. Printer - The Printer is defined as the person who creates the Resource that is delivered. This includes all suppliers, (e.g., binders, prepress suppliers, etc.). Buyer - The customer specified in CustomerInfo . Other - The Contact [@ ContactTypes = "DeliveryCharge" ]. New in JDF 1.2 |
||
|
Specifies the earliest time after which the transfer is to be made. Within an RFQ or a Quote, at most one of Earliest or EarliestDuration must be specified. |
||
|
Specifies the earliest time by which the transfer is to be made relative to the date of the purchase order. Within an RFQ or a Quote, at most one of Earliest or EarliestDuration must be specified. Within a purchase order, EarliestDuration must not be specified. |
||
|
Specifies a delivery method, which can be a generic method. BestWay - The sender decides how to deliver. Storage - The product is stored by the supplier. UPS - a delivery service brand |
||
|
Point of transfer of ownership: Origin - Ownership of goods is transferred upon leaving point of origin. Destination - Ownership is transferred upon receipt at destination. |
||
|
Percentage value that defines the acceptable upwards variation of Amount . Defaults to the trade custom defaults as defined by PIA, BVD, etc. |
||
|
Specifies whether the delivery brings or picks up the merchandise. If Pickup = "false" , the drop is delivered to the address specified in Company . If Pickup = "true" , the DeliveryIntent describes an input to the Job, (e.g., a CD for inserting, a preprinted cover, etc.). In this case Company describes the location where the merchandise is picked up. |
||
|
Specifies the time by which the transfer is to be made. Within an RFQ or a Quote, exactly one of Required or RequiredDuration must be specified. |
||
|
Specifies the time by which the transfer is to be made relative to the date of the purchase order. Within an RFQ or a Quote, exactly one of Required or RequiredDuration must be specified. Within a purchase order, RequiredDuration must not be specified. |
||
|
Specifies a delivery method for returning the surplus material and must not be specified unless SurplusHandling = "Return" . |
||
|
The service level of the specific carrier. Values include those from: ArtDeliveryIntent / ServiceLevel |
||
|
Describes what is to happen with unused or redundant parts of the transfer specified with
Transfer
=
"BuyerToPrinterDeliver"
or
"BuyerToPrinterPickup"
after the Job. The return delivery or pickup address is specified by ReturnWithProduct - The surplus material is delivered back to the customer together with the final product. Return - The surplus material is delivered back independently directly after usage. Pickup - The customer picks up the surplus material. Destroy - The printer destroys the surplus material. PrinterOwns - The surplus material belongs to the printer. Store - The printer has to store the surplus material for future purposes. |
||
|
Describes the direction and responsibility of the transfer.
BuyerToPrinterDeliver
- The
DeliveryIntent
describes an input to the Job, (e.g., a CD for inserting, a preprinted cover, etc.). In this case, the buyer delivers the merchandise to the printer. The printer is to specify in the quote a special
BuyerToPrinterPickup
- The
DeliveryIntent
describes an input to the Job, (e.g., a CD for inserting, a preprinted cover, etc.). In this case, the printer picks up the merchandise. PrinterToBuyerDeliver - The DeliveryIntent describes an output of the Job. In this case, the printer delivers the merchandise to the buyer. The Contact [contains (@ ContactTypes , "Delivery" )] specifies where the printer is to send the merchandise. PrinterToBuyerPickup - The DeliveryIntent describes an output of the Job. In this case, the buyer picks up the merchandise. The printer is to specify in the quote a special Contact [contains (@ ContactTypes , "Pickup" )]. The Contact specifies where the buyer is to pick up the merchandise. |
||
|
Percentage value that defines the acceptable downwards variation of Amount . Defaults to the trade custom defaults as defined by PIA, BVD, etc. |
||
|
Company ? |
||
|
Contact * |
Address and further information of the Contact responsible for the transfer. The actual delivery address is specified as the Contact [contains (@ ContactTypes , "Delivery" )]/ Address . The actual pickup address is specified as the Contact [contains (@ ContactTypes , "Pickup" )]/ Address . At most one Contact [contains (@ ContactTypes , X )] must be specified for X equal to "Delivery" , "Pickup" or "Billing" , |
|
|
Includes all locations where the product will be delivered. Note that multiple DropIntent Elements specify multiple deliveries and not options for delivery. |
||
|
Pricing ? |
Pricing Elements that define the pricing of the complete DeliveryIntent including any DropIntent or DropItemIntent Elements that may contain further Pricing Elements. In JDF 1.3 and beyond, pricing information has been removed and will be handled by the business wrapper around JDF, e.g. PrintTalk. |
7.1.5.1 Element: DropIntent
This Element contains information about the intended individual drop of a delivery. Attributes that are specified in a DropIntent Element overwrite those that are specified in their parent DeliveryIntent Element. If optional values are not specified, they default to the values specified in the DeliveryIntent .
|
Number of components used to calculate the value of the AdditionalPrice Attribute in the Pricing . This value applies to the number of additional items in one DropIntent / DropItemIntent and not to the total additional number of items. If not specified, defaults to the value of DeliveryIntent /@ AdditionalAmount . In JDF 1.3 and beyond, pricing information has been removed and will be handled by the business wrapper around JDF, e.g. PrintTalk. |
||
|
Account ID of the buyer with the delivery service. Default value is from: DeliveryIntent /@ BuyerAccount |
||
|
Specifies the earliest time after which the transfer is to be made. Within an RFQ or a Quote, at most one of Earliest or EarliestDuration must be specified. |
||
|
Specifies the earliest time by which the transfer is to be made relative to the date of the purchase order. Within an RFQ or a Quote, at most one of Earliest or EarliestDuration must be specified. Within a purchase order, EarliestDuration must not be specified. |
||
|
Default value is from: DeliveryIntent Method . Values include those from: DeliveryIntent Method |
||
|
If "true" , the merchandise is picked up. If Pickup = "false" , the DropIntent is delivered to the address specified in Company . If Pickup = "true" , the DropIntent describes an input to the Job, (e.g., a CD for inserting, a preprinted cover, etc.). In this case, Company describes the location where the merchandise is picked up. |
||
|
Specifies the time by which the delivery is to be made. Within an RFQ or a Quote, at most one of Required or RequiredDuration must be specified. |
||
|
Specifies the time by which the delivery is to be made relative to the date of the purchase order. Within an RFQ or a Quote, at most one of Required or RequiredDuration must be specified. Within a purchase order, RequiredDuration must not be specified. |
||
|
Specifies a delivery method for returning the surplus material, and must not be specified unless SurplusHandling = "Return" . Default value is from: DeliveryIntent / ReturnMethod . Values include those from: DeliveryIntent / ReturnMethod |
||
|
The service level of the specific carrier. Default value is from: DeliveryIntent / ServiceLevel . Values include those from: DeliveryIntent / ServiceLevel |
||
|
Describes what is to happen with unused or redundant parts of the transfer. Default value is from: DeliveryIntent SurplusHandling . Values are from : DeliveryIntent / SurplusHandling . |
||
|
Describes the direction and responsibility of the transfer. Default value is from: DeliveryIntent / Transfer . Values are: (see DeliveryIntent / Transfer ). |
||
|
Company ? |
Address and further information of the addressee. In JDF 1.1 and beyond Company is a Subelement of Contact . |
|
|
Contact * |
Address and further information of the Contact responsible for the transfer. The actual delivery address is specified as the Contact [contains (@ ContactTypes , "Delivery" )]/ Address . The actual pickup address is specified as the Contact [contains (@ ContactTypes , "Pickup" )]/ Address . At most one Contact [contains (@ ContactTypes , X )]/ must be specified for X equal to "Delivery" , "Pickup" or "Billing" . Defaults to the DeliveryIntent / Contact |
|
|
A DropIntent may consist of multiple products, which are represented by their respective Physical Resource s. Each DropItemIntent Element describes a number of individual Resources that is part of this DropIntent . |
||
|
Pricing ? |
Pricing Element that defines the pricing of the DropIntent . In JDF 1.3 and beyond, pricing information has been removed and will be handled by the business wrapper around JDF, e.g. PrintTalk. |
7.1.5.2 Element: DropItemIntent
|
Number of components used to calculate the value of the AdditionalPrice Attribute in the Pricing . If not specified, defaults to the value of DropIntent /@ AdditionalAmount . In JDF 1.3 and beyond, pricing information has been removed and will be handled by the business wrapper around JDF, e.g. PrintTalk. |
||
|
Specifies the final number of Resources delivered. If not specified, defaults to the total amount of the Resource that is specified by PhysicalResource or 1 if this DropItemIntent specifies a proof. Note that DropItemIntent /@ Amount corresponds semantically to ResourceLink /@ ActualAmount and DropItem /@ ActualAmount . |
||
|
Specifies the original number of Resources ordered. If not specified, defaults to the value of Amount . Note that DropItemIntent /@ OrderedAmount corresponds semantically to ResourceLink /@ Amount and DropItem /@ Amount . |
||
|
This DropItemIntent refers to a proof that is specified in a ProofItem of the ProofingIntent of this Product Intent Node. Constraint: ProofingIntent / ProofItem /@ ProofName must match Proof . Exactly one of PhysicalResource or Proof must be specified. |
||
|
Unit of measurement for the Amount specified in the PhysicalResource . Default value is: value of Unit defined in the Resource described by the PhysicalResource |
||
|
Description of the individual item that is delivered. Constraint: exactly one of PhysicalResource or Proof must be specified. Note: PhysicalResource represents a Resource that must be an instance of a Physical Resource , (e.g., Component ). |
||
|
Pricing ? |
Pricing Element that defines the pricing of the DropItemIntent . Deprecation note: starting with JDF 1.3, pricing information has been removed and will be handled by the business wrapper around JDF, e.g. PrintTalk. |
7.1.5.3 Element: Pricing
The table defining the deprecated Pricing Subelement has been moved to Section P.4.2, “DeliveryIntent Deprecated Subelements” .
7.1.5.4 Element: Payment
The table defining the deprecated Payment Subelement has been moved to Section P.4.2, “DeliveryIntent Deprecated Subelements” .
7.1.5.5 Element: CreditCard
The table defining the deprecated CreditCard Subelement has been moved to Section P.4.2, “DeliveryIntent Deprecated Subelements” .
7.1.6 EmbossingIntent
This Resource specifies the embossing and/or foil stamping intent for a JDF Job using information that identifies whether the product is embossed or stamped, and if desired, the complexity of the affected area.
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Each embossed image is described by one EmbossingItem . |
7.1.6.1 Element: EmbossingItem
|
Both - Both debossing and embossing in one stamp. Flat - The embossing foil is applied flat. Used for foil stamping. New in JDF 1.3 |
||
|
The angle of a beveled edge in degrees. Typical values are an angle of: 30, 40, 45, 50 or 60 degrees. If EdgeAngle is specified, EdgeShape = "Beveled" must be specified. |
||
|
The transition between the embossed surface and the surrounding media can be rounded or beveled (angled). |
||
|
The strings defined in EmbossingType are whitespace separated combinations of the following tokens. Braille - 6 dot Braille embossing. New in JDF 1.4 BlindEmbossing - Embossed forms that are not inked or foiled. The color of the image is the same as the paper. FoilEmbossing - Combines embossing with foil stamping in one single impression. FoilStamping - Using a heated die to place a metallic or pigmented image from a coated foil on the paper. RegisteredEmbossing - Creates an embossed image that exactly registers to a printed image. |
||
|
Defines the color of the foil material which is used for embossing. Values are from : Table A-3, “NamedColor Enumeration Values”. |
||
|
A more specific, specialized or site-defined name for the color. If FoilColorDetails is supplied, FoilColor SHOULD also be supplied. |
||
|
The height of the levels. This value specifies the vertical distance between the highest and lowest point of the stamp, regardless of the value of Direction . |
||
|
Position of the center of the bounding box of the embossed image in the coordinate system of the Component . |
7.1.7 FoldingIntent
This Resource specifies the fold intent for a JDF Job using information that identifies the number of folds, the height and width of the folds, and the folding catalog number. Note that the folding catalog is described in Section 7.2.79, “FoldingParams” .
CreasingParams , CuttingParams , Fold , FoldingParams , PerforatingParams
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Describes the folding scheme according to the folding catalog in Figure 7-33, “Fold catalog part 1” and Figure 7-34, “Fold catalog part 2”. Value format is: " Fn-i " where “n” is the number of finished pages and “i” is either an integer, which identifies a particular fold or the letter "X" , which identifies a generic fold. E.g., "F6-2" describes a Z-fold of 6 finished pages, and "F6-X . " describes a generic fold with 6 finished pages. Note: The folding scheme in this context refers to the folding of the finished product as seen after the cutting, not the folding, of the Sheet as seen in production. See LayoutIntent /@ Foliocount for a discussion of pagination of folded end products. |
||
|
Number of folds in x and in y direction. This Attribute specifies the number of folds seen in the Sheet after folding, and not the number of fold operations needed to achieve that result. If not specified, it
must
be inferred from
FoldingCatalog
. If X and Y are the number of folds in the x and y directions, respectively, the product
2*(X+1)*(Y+1
)
must
always match the n of |
||
|
Fold * |
This describes the details of folding operations in the sequence described by the value of FoldingCatalog . Fold must be specified if non-symmetrical folds are requested. |
7.1.8 HoleMakingIntent
This Resource specifies the holemaking intent for a JDF Job, using information that identifies the type of holemaking operation or alternatively, an explicit list of holes. This Resource does not specify whether the media will be pre-drilled or the media will be drilled or punched as part of making the product.
Hole , HoleLine , HoleMakingParams , Media
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Size (bounding box) of the hole in points when specifying a standard hole pattern in HoleType . If not specified the implied default defined in Appendix L, “JDF/CIP4 Hole Pattern Catalog” is assumed. Ignored when HoleType /@ Actual = "Explicit" . |
||
|
The edge of the media relative to where the holes are to be punched. Use with HoleType . Pattern - Specifies that the reference edge implied by the value of HoleType in Appendix L, “JDF/CIP4 Hole Pattern Catalog” is used. |
||
|
Predefined hole pattern. Multiple hole patterns are specified as one NMTOKENS string, (e.g., 3-hole ring binding and 4-hole ring binding holes on one piece of media). Explicit - Holes are defined in an array of Hole Elements. 2HoleEuro - Replace by either R2m-DIN or R2m-ISO Deprecated in JDF 1.0 . 3HoleUS - Replace by R3I-US Deprecated in JDF 1.0 4HoleEuro - Replace by R4m-DIN-A4 or R4m-DIN-A5 Deprecated in JDF 1.0 . Values are from : Appendix L, “JDF/CIP4 Hole Pattern Catalog”. |
||
|
HoleList ? |
Array of all Hole Elements. Used only when HoleType /@ Actual = "Explicit" , otherwise this Element is not used. |
7.1.9 InsertingIntent
This Resource specifies the placing or inserting of one component within another, using information that identifies page location, position and attachment method. The receiving component is defined by a ProcessUsage Attribute of “Parent”. All other input components are mapped to the Insert Elements by their ordering in the ResourceLinkPool .
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
7.1.9.1 Element: InsertList
|
Insert * |
7.1.9.2 Element: Insert
|
List of potential Folios where the insert is to be placed. A Folio is defined by its first page in case Method /@ Actual = "BlowIn" and by the page that the glue is applied in case Method /@ Actual = "BindIn" . In general, a list of Folios will only be supplied for Method /@ Actual = "BlowIn" . The pages are counted in the order, which is described in FolioCount of the parent Component / Bundle . |
||
|
Glue used to fasten the insert. Default value is fro m: InsertingIntent / GlueType . |
||
|
Default value is from : InsertingIntent / Method . |
||
|
Offset between the Component to be inserted and finished page identified by Folio in the parent Component . In JDF 1.2 and beyond, the offset is specified in the offset part of Transformation . |
||
|
Rotation and offset between the Component to be inserted and the parent Component . If not specified, the identity matrix is applied. |
||
|
List of finished pages of the cover that wrap around an Insert after all folds are correctly positioned. It is sufficient to specify the finished page of the front surface of the cover, (e.g., Cover 1 and Cover 4). Note that this key must not be specified unless the folding is ambiguous. |
||
|
GlueLine * |
Array of all GlueLine Elements used to glue in the insert. must not be specified in conjunction with GlueType . |
7.1.10 LaminatingIntent
This Resource specifies the laminating intent for a JDF Job using information that identifies whether or not the product is laminated, and if desired, the temperature and thickness of the laminate.
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
If "true" , the product is laminated. If no LaminatingIntent is specified, the product must not be laminated. |
||
|
Temperature used in the Laminating Process. |
||
|
The intended texture of the laminate. Antique - Rougher than vellum surface. Calendared - Extra-smooth or polished, uncoated paper. |
||
|
Thickness of the laminating material. Measured in microns [m]. |
7.1.11 LayoutIntent
This Resource records the size of the finished pages for the product component. It does not, however, specify the size of any intermediate results such as press Sheets. It also describes how the finished pages of the product component are to be imaged onto the finished media. The size definition of the finished media describes the size of a Sheet that is folded to create a product, not the size of a production Sheet, (e.g., in the press).
Layout , LayoutPreparationParams , StrippingParams
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Specifies the width (X) and height (Y) in points, respectively, of the media or product Component unfolded. For example, Dimensions for a Z-fold is the unfolded dimensions, while FinishedDimensions is the folded dimensions if known. Use Dimensions if FinishedDimensions is not known. The Dimensions Span Element is provided for the rare case that FinishedDimensions does not unambiguously define the finished product, due to complex folding schemes. If both values are specified, FinishedDimensions takes precedence |
||
|
Specifies the width (X), height (Y) and depth (Z) in points, respectively, of the finished product Component after all finishing operations, including folding, trimming, etc. If the Z coordinate is 0, it is ignored. Only FinishedDimensions should be specified if both FinishedDimensions and Dimensions are known. 
|
||
|
Specifies the media grain direction of the finished page with respect to the binding edge. ParallelToBind - Grain direction is parallel to the binding edge. PerpendicularToBind - Grain direction is perpendicular to the binding edge. Note: in JDF 1.2 this was erroneously misspelled as PerpendiculatToBind |
||
|
Indicates the desired orientation of the finished media. Portrait - The short edges of the media are the top and bottom. Landscape - The long edges of the media are the top and bottom. Note: In JDF 1.1, the finished page orientation is implied by the value of Dimensions and FinishedDimensions . If height (X) > width (Y), the product is portrait. |
||
|
Defines the method used when counting finished pages. Booklet - Each sample of the component consists of two finished pages, (e.g., a leaf--the front side and the back side of one sample of the component). Folds as specified by FoldingIntent /@ FoldingCatalog do not affect pagination. Finished Pages are counted in reader order of the pages of the component in the product. Flat - The number of finished pages of one Sheet of an individual component is given by the product 2*(X+1)*(Y+1) , where x denotes the number of folds in x direction and y denotes the number of folds in y direction. The pages are counted from the upper left of the front side of the top media to the lower right of the back side of the bottom media. Flat is to be used for non-standard products where the reader order is ambiguous. The page breaks on a Sheet are defined by the folds as specified by FoldingIntent /@ FoldingCatalog (see Figure 7-33 and Figure 7-34) for the product. All Sheets are counted, even if they are not included in the product, (e.g., due to a ShapeCuttingIntent ). |
||
|
Specifies a regular, multi-up grid of page cells into which content pages are mapped. 
The first value specifies the number of columns of page cells and the second value specifies the number of rows of page cells in the multi-up grid (both numbers are integers). At most one of Layout or NumberUp must be specified. |
||
|
Specifies the number of finished pages (surfaces) of the product component, including blank pages. Pages multiplied with Dimensions then divided by two (2) identifies the amount of paper that is used in the product. Pages describes the paper usage regardless of document layout. This value must be an even number. For example, the value for Pages for a two-sided booklet with seven Reader Pages would be "8" , whether the booklet were saddle stitched or glued. 
|
||
|
Specifies the number of non-identical finished pages of the product component, (i.e., the number of distinct master pages copied to produce the product). If not specified, the value of Pages is used as the default. For example, if there are ten finished pages, in which three are identical, PageVariance /@ Actual = "8" since it would take eight master copies to produce the product. |
||
|
Specifies the policy to automatically rotate the image to optimize the fit of the image to the page container. For instance, individual landscape pages in a portrait document may automatically be rotated. The page container is one cell on the NUp grid of the Media defined in Dimensions or FinishedDimensions . RotateOrthogonal - Rotate by 90˚ in either direction. |
||
|
Indicates whether contents are to be printed on one or both sides of the media. OneSided - Page contents will only be imaged on the front side of the media. OneSidedBack - Page contents will only be imaged on the back side of the media. New in JDF 1.2 TwoSidedHeadToHead - Impose pages upon the front and back sides of media Sheets so that the head (top) of page contents back up to each other. TwoSidedHeadToFoot - Impose pages upon the front and back sides of media Sheets so that the head (top) of the front backs up to the foot (bottom) of the back. |
||
|
Allows printing even if the container size defined in Dimensions or FinishedDimensions does not match the requirements of the data. The page container is one cell on the NUp grid of the Media defined in Dimensions or FinishedDimensions . ClipToMaxPage - The page contents is to be clipped to the size of the container. The printed area is centered in the source image. FitToPage - The page contents is to be scaled up or down to fit the container. The aspect ratio is maintained. ReduceToFit - The page contents is to be scaled down but not scaled up to fit the container. The aspect ratio is maintained. Tile - The page contents is to be split into several tiles, each printed on its own container. |
||
|
Layout ? |
Specifies the details of a more complex Layout . At most one of Layout or NumberUp must be specified. Note that the Layout specified in LayoutIntent specifies the layout definition of the finished product and not the layout of the production Sheets. |
7.1.12 MediaIntent
This Resource describes the media to be used for the product component. In some cases, the exact identity of the medium is known, while in other cases, the characteristics are described and a particular stock is matched to those characteristics.
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Identical to FrontCoatings , but applied to the back surface of the media. |
||
|
Reflectance percentage of diffuse blue reflectance as defined by [ISO2470:1999] . The reflectance is reported per [ISO2470:1999] as the diffuse blue reflectance factor of the paper or board in percent to the nearest 0.5% reflectance factor. |
||
|
Indicates whether the customer will supply the media. Note that the Media Resource can be used to specify additional media requirements, particularly when the media is supplied by the customer. |
||
|
Specifies the size of the supplied media in points if BuyerSupplied evaluates to "true" . Dimensions must be ignored if BuyerSupplied evaluates to "false" . Note that the size of the finished product is always specified in LayoutIntent / FinishedDimensions . In JDF 1.2 and beyond the specifics of BuyerSupplied media should be specified using a Media Resource. The dimensions of the finished product are specified with LayoutIntent / Dimensions or LayoutIntent / FinishedDimensions . |
||
|
Single, capital letter that specifies the Flute type of corrugated media. Although the classification of flutes using a letter code “A”, “B”, etc., are used very frequently e.g., in the specification of the order for a box, there seems to be no agreement on the exact numerical specification of those categories. Slightly varying numbers for flute size and frequency can be found between regions (European versus US) and between vendors. Values include those from: Media /@ Flute |
||
|
Direction of the fluting. Values are the same as Media /@ FluteDirection with slightly different description. LongEdge - Along the longer axis as defined by LayoutIntent / Dimensions . ShortEdge - Along the shorter axis as defined by LayoutIntent / Dimensions . XDirection - Along the X-axis of the LayoutIntent coordinate system YDirection - Along the Y-axis of the LayoutIntent coordinate system |
||
|
What pre-process coating has been applied to the front surface of the media. Coated - A coating of a system specified type. New in JDF 1.2 InkJet - A coating intended for use with inkjet technology. New in JDF 1.2 |
||
|
The intended grade of the media on a scale of 1 through 5. Grade is ignored if MediaType /@ Actual is not "Paper" . Grade of paper material is defined in accordance with the paper “types” set forth in [ISO12647-2:2004] . Offset printing paper types are defined with integer values: Note: [ISO12647-2:2004] paper type AdditionalPrice values do not align with U.S. GRACOL paper grade AdditionalPrice values, (i.e., [ISO12647-2:2004] type 1 does not equal U.S. GRACOL grade 1.) |
||
|
Direction of the grain in the coordinate system defined by LayoutIntent / Dimensions or LayoutIntent / FinishedDimensions . ShortEdge - Parallel to the shorter axis of the finished page. LongEdge - Parallel to the longer axis of the finished page. XDirection - Along the X-axis of the LayoutIntent coordinate system New in JDF 1.4 YDirection - Along the Y-axis of the LayoutIntent coordinate system. New in JDF 1.4 |
||
|
The intended number of holes that are to be punched in the media (either pre- or post-punched.) In JDF/1.1, use HoleType which includes the number of holes. |
||
|
Predefined hole pattern that specifies the pre-punched holes in the media. Multiple hole patterns are specified as one NMTOKENS string, (e.g., 3-hole ring binding and 4-hole ring binding holes on one piece of media.) Values include those from: Appendix L, “JDF/CIP4 Hole Pattern Catalog” . |
||
|
Color of the media. If more-specific, specialized or site-specific media color names are needed, use MediaColorDetails . Values are from : Table A-3, “NamedColor Enumeration Values”. |
||
|
A more specific, specialized or site-defined name for the media color. If MediaColorDetails is supplied, MediaColor S HOULD also be supplied. Note that there is a one-to-many relationship between entries in MediaColor and MediaColorDetails , (e.g., MediaColorDetails values of "Burgundy" and "Ruby" both correspond to a MediaColor of "DarkRed" ). |
||
|
Named quality description of the media. For folding carton quality, multiple named quality description systems are in use. E.g. GC1, SBB, etc. For an overview see |
||
|
When the input media is grouped in sets, identifies the number of pieces of media in each set. For example, if the UserMediaType is "PreCutTabs" , a MediaSetCount of 5 would indicate that each set includes 5 tab Sheets. |
||
|
Describes the medium being employed. CorrugatedBoard New in JDF 1.3 Disc - CD or DVD disc to be printed on. New in JDF 1.2 Other - Any other media. For this value MediaTypeDetails should also be specified |
||
|
Describes additional details of the medium described in MediaType . Cloth - Cloth, e.g., for a hard cover book case. Leather - Leather, e.g., for a hard cover book case. Values include those from: Media /@ MediaTypeDetails Note: values from Media /@ MediaTypeDetails are RECOMMENDED. However, some Process related values, such as DryFilm, SHOULD NOT be used for this Attribute. |
||
|
Describes the format of the media as it is delivered to the Device. Deprecation note: deprecated because Intent Attributes and Span Elements pertain to finished product, not the raw media format. If BuyerSupplied = "true" , then the Media Resource can be used to provide this Span Element. |
||
|
The opacity of the media. See OpacityLevel to specify the degree of opacity for any of these values. Opaque - The media is opaque. With two-sided printing the printing on the other side does not show through under normal incident light. Translucent - The media is translucent to a system specified amount. For example, translucent media can be used for back lit viewing. New in JDF 1.2 Transparent - The media is transparent to a system specified amount. |
||
|
Normalized TAPPI opacity, (Cn), as defined and computed in [ISO2471:1998] . Refer also to [TAPPI T519] for calculation examples. |
||
|
If "true" , recycled media is requested. In JDF 1.2 and beyond, use RecycledPercentage . |
||
|
The percentage, between 0 and 100, of recycled material that the media is expected to contain. |
||
|
Strings providing available brand names. The customer might know exactly what paper is to be used. Example is “Lustro” or “Warren Lustro” even though the manufacturer name is included. |
||
|
Strings describing the available stock. Values include those from: Media / @StockType |
||
|
The intended texture of the media. Values include those from: Media / @Texture . |
||
|
The thickness of the chosen medium. Measured in microns [m]. |
||
|
A human-readable description of the type of media. The value can be used by an operator to select the correct media to load. The semantics of the values will be site-specific. Continuous - Continuously connected Sheets of an opaque material. Which edge is connected is not specified. ContinuousLong - Continuously connected Sheets of an opaque material connected along the long edge. ContinuousShort - Continuously connected Sheets of an opaque material connected along the short edge. Envelope - Envelopes that can be used for conventional mailing purposes. EnvelopePlain - Envelopes that are not preprinted and have no windows. EnvelopeWindow - Envelopes that have windows for addressing purposes. FullCutTabs - Media with a tab that runs the full length of the medium so that only one tab is visible extending out beyond the edge of non-tabbed media. Labels - Label stock, (e.g., a Sheet of peel-off labels). Letterhead - Separately cut Sheets of an opaque material including a letterhead. MultiLayer - Form medium composed of multiple layers which are preattached to one another, (e.g., for use with impact printers). MultiPartForm - Form medium composed of multiple layers not preattached to one another; each Sheet may be drawn separately from an input source. Photographic - Separately cut Sheets of an opaque material to produce photographic quality images. PreCutTabs - Media with tabs that are cut so that more than one tab is visible extending out beyond the edge of non-tabbed media. Stationery - Separately cut Sheets of an opaque material. TabStock - Media with tabs (either precut or full-cut). Transparency - Separately cut Sheets of a transparent material. |
||
|
The intended weight of the media, measured in pounds per ream of basis size. At most one of Weight or USWeight must be specified. If known, Weight should be specified in grammage ( g /m2.) In JDF 1.2 and beyond, use Weight . |
||
|
The intended weight of the media, measured in grammage ( g /m2) of the media. See Appendix F, “North American and Japanese Media Weight Explained” for an explanation of how to calculate the US weight from the grammage for different stock types. |
||
|
Subelement describing the layer structure of media such as corrugated or self adhesive materials. |
7.1.13 NumberingIntent
This Resource describes the parameters of stamping or applying variable marks in order to produce unique components, for items such as lottery notes or currency.
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Defines the color of the numbering. Values are from : Table A-3, “NamedColor Enumeration Values”. |
||
|
A more specific, specialized or site-defined name for the color. If ColorNameDetails is supplied, ColorName SHOULD also be supplied. |
||
7.1.13.1 Element: NumberItem
|
Defines the color of the numbering. Default value is from: NumberingIntent /@ ColorName . Values are from : Table A-3, “NamedColor Enumeration Values”. |
||
|
A more specific, specialized or site-defined name for the color. If ColorNameDetails is supplied, ColorName SHOULD also be supplied. |
||
|
Rotation of the numbering machine in degrees. If Orientation/@ Actual = 0, the top of the numbers is along the leading edge. |
||
|
Number that specifies the difference between two subsequent numbers of the numbering machine. |
||
|
Specifies the name of the Color in the ColorPool that is used for Numbering. |
7.1.14 PackingIntent
This Resource specifies the packaging intent for a JDF Job, using information that identifies the type of package, the wrapping used, and the shape of the package. Note that this specifies packing for shipping only, not packing of items into custom boxes, etc. Boxes are convenience packaging and are not envisioned to be protection for shipping. Cartons perform this function. All quantities are specified as finished pieces per wrapped/boxed/carton or palletized package. The model for packaging is that products are wrapped together, wrapped packages are placed in boxes , boxes are placed in cartons , and cartons are stacked on pallets .
BoxPackingParams , Bundle , Component , PalletizingParams , Pallet , ShrinkingParams , StackingParams , Strap , StrappingParams , WrappingParams
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Describes the length, width and height of the box, in points. |
||
|
Describes the length, width and height of the carton, in points. For example, 288 544 1012 |
||
|
Describes the folding scheme for folding the product for packaging as specified in the folding catalog in Figure 7-33, “Fold catalog part 1” and Figure 7-34, “Fold catalog part 2”. Value format is: " Fn-i " where “n” is the number of finished pages and “i” is either an integer, which identifies a particular fold or the letter "X" , which identifies a generic fold. E.g., "F6-2" describes a Z-fold of 6 finished pages, and "F6-X . " describes a generic fold with 6 finished pages. Note: The folding scheme in this context refers to the folding of the finished product for packaging only. The folding has no effect on the page/Folio definition. |
||
|
Additional protective corner boards for packaging on a pallet: |
||
|
Describes the length and width of the pallet, in points, (e.g., "3500 3500" ). |
||
|
Wrapping of the completed pallet. |
||
7.1.15 ProductionIntent
This Resource specifies the manufacturing intent and considerations for a JDF Job using information that identifies the desired result or specified manufacturing path.
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Balanced - Request for a manufacturing process that balances the requirements for cost, speed and quality. CostEffective - Request for the most cost effective manufacturing process. Fastest - Request for the most time effective manufacturing process. Cost and Quality can be sacrificed for a fast turnaround time. HighestQuality - Request for the manufacturing process which will result in the highest quality. |
||
|
Lithography - Includes offset printing Modification Note: starting with JDF 1.3, the data type of PrintProcess is expanded from EnumerationSpan to NameSpan . |
||
|
Resource * |
Any production Resources that are provided by the customer. Some examples include buyer specified media or ink or specific parameter setups. Note that DeliveryIntent must be specified for any PhysicalResource Elements that are physically supplied by the customer. |
7.1.16 ProofingIntent
This Resource specifies the prepress proofing intent for a JDF Job using information that identifies the type, quality, brand name and overlay of the proof. The proofs defined in ProofingIntent define the proofs that will be provided to the customer and does not specify internal production proofs. The delivery options of proofs are specified in DeliveryIntent .
ApprovalParams , ApprovalSuccess , ColorantControl , ColorSpaceConversionParams , ExposedMedia , ImageSetterParams , InterpretingParams , Layout , Media , RenderingParams , ScreeningParams , SeparationControlParams , StrippingParams
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
Specifies the details of the proofs that are needed. If no ProofItem exists in a ProofingIntent , it explicitly specifies that no proofs are desired. |
7.1.16.1 Element: ProofItem
All parameters of ProofingIntent have been moved into ProofItem in JDF 1.1
|
Specifies the total number of copies of this proof that is needed. If not specified, it defaults to an IntegerSpan with Preferred = "1" . |
||
|
Monochrome - Generic single color printing condition, (e.g., black and white or one single spot color). BasicColor - Color does not match precisely. This implies the absence of a color matching system. MatchedColor - Color is matched to the output of the press using a color matching system. |
||
|
Requires proof to be a legally binding, accurate representation of the image to be printed, (i.e., color quality requirements have been met when the printed piece acceptably matches the proof). |
||
|
Identifies which images (OPI or other) will be printed on a proof or displayed as a soft proof. NoImages - No images are imaged on the proof. LowResolution - Low resolution images are imaged on the proof. HighResolution - High resolution production images are imaged on the proof, resulting in proofs that accurately represent the final product. |
||
|
Index list of pages that are to be proofed in the ArtDeliveryIntent / RunList / PageList . If no range is specified then all pages MUST be proofed. |
||
|
Name of the ProofItem . This field must be specified if delivery of a proof is specified in DeliveryIntent . |
||
|
Identifies a remote target for the proof output in a remote proofing environment. This can be either a soft or a hard proofing target. The file to be displayed or output is to be sent to the URL specified in ProofTarget . |
||
|
Separations that are to be proofed. If not specified, all separations are proofed. |
||
|
List of people (e.g., a customer, printer or manager) who can sign the ApprovalSuccess . |
7.1.17 PublishingIntent
PublishingIntent specifies publishing metadata that are of general interest for prepress, press and postpress. The data include details on the general structure of product being published.
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
IDs of ContentData Elements in the referenced ContentList . ContentData Elements provide metadata related to the product to be published. ContentDataRefs MUST NOT be specified if no ContentList is specified. |
||
|
Defines the product type of the issue. Magazine - The publication is a magazine Newspaper - The publication is a newspaper Supplement - The publication is a supplement to a magazine or newspaper. New in JDF 1.4. |
||
|
ContentList with additional metadata. |
7.1.18 ScreeningIntent
This Resource specifies the screening intent parameters desired for a JDF Job.
ScreeningParams , SeparationControlParams
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
7.1.19 ShapeCuttingIntent
This Resource specifies form and line cutting for a JDF Job. The cutting Processes are applied for producing special shapes like an envelope window or a heart-shaped beer mat. Information that identifies the type and shape of cuts can be described. The Cutting Process(es) can be performed using tools such as hollow form punching, perforating or die-cutting equipment.
CuttingParams , ShapeCuttingParams
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”)
|
ShapeCut * |
Array of all ShapeCut Elements. Used when each shape is exactly specified. |
7.1.19.1 Element: ShapeCut
|
Specification of a rectangular window. (See Section A.2.32, “rectangle” for a definition of the rectangle data type.) |
||
|
If "true" , the inside of a specified shape is to be removed. If "false" , the outside of a specified shape is to be removed. An example of an inside shape is a window, while an example of an outside shape is a shaped greeting card. |
||
|
Specification of a complex path. This may be an open path in the case of a single line. |
||
|
Transparent material that fills a shape (e.g., an envelope window) that was cut out when CutOut = "true" . |
||
|
Type of cut or perforation used. Perforate - Interrupted perforation that does not span the entire Sheet. |
||
|
Depth of the shape cut. Measured in microns [m]. If not specified, the shape is completely cut. |
||
|
List of Finished Pages to which this shape is to be applied. Only the recto finished page of a leaf should be specified. |
||
|
Describes any precision cutting other than hole making. RoundedRectangle - Rectangle with rounded corners. New in JDF 1.3 |
||
|
Number of teeth in a given perforation extent in teeth/point. MicroPerforation is defined by specifying a large number of teeth (n > 1000). |
7.1.20 SizeIntent
SizeIntent has been deprecated in JDF 1.1. All contents have been moved to LayoutIntent .
7.2 Process Resources
The rest of the Resources described in this chapter are what are known as Process Resources. This means that they serve as necessary components in each of the JDF Processes. Section 7.2.1 describes the template for all of the sections that follow. Then every Resource already defined for JDF is chronicled, in alphabetical order, below.
7.2.1 Process Resource Template
Each of the following sections begins with a brief narrative description of the Resource. Following that is a list containing details about the properties of the Resource, as shown below. The first item in the list provides the Class of the Resource. As was described in Section 3.8.5, “Resource Classes”, all Resources are derived from one of the following seven superclasses: Intent , Parameter , Implementation , Consumable , Quantity , Handling and PlaceHolder . All Resources inherit additional contents (i.e., zero or more Attributes or zero or more Elements) from their respective superclasses, and those Attributes and Elements are not repeated in this section. Thus those Attributes associated with a Resource of Class Parameter , for example, can be found in Table 3-10, “Abstract Resource Element”. Note that this inheritance is only valid for atomic Resources, (i.e., Resources that reside directly in a ResourcePool ).
Resource Elements are listed in separate sections if they can be referenced by more than one Resource. For an example, see the Resource Element SeparationSpec . If the Resource is not referenced by multiple Resources, it is described inside the Resource section of the Resource to which it belongs. For example, see the Structure of the BundleItem Element of the Bundle Resource. If an Element inside a Resource section of the Resource is needed to be referenced by multiple Resources in a revision of JDF, then that Element is promoted to its own section. For example, ColorSpaceConversionOp was a Subelement of ColorSpaceConversionParams in JDF/1.1. The Resource Class of an atomic Resource also defines the superclasses from which the Resource inherits additional contents. The Consumable Resource , Quantity Resource and Handling Resource inherit from the Physical Resource Element, which in turn inherits from the Resource Element. The Parameter Resource and Implementation Resource Elements inherit from the Resource Element directly. Non-atomic Resources (i.e., Resource Subelements) do not inherit contents from Resource superclasses.
Examples for Resources that can be used as atomic Resources or Resource Elements are: Employee , InsertSheet , LayoutElement and Media .
After the list describing the Resource properties, each section contains tables that outline the structure of each Resource and, when applicable, the abstract or Subelement information that pertains to the Resource structure. The first column contains the name of the Attribute or Element. In some cases, a Resource will contain multiple Elements of the same type. If this is the case, the Element name is listed as often as it appears, along with a term in parentheses that identifies the occurrence. For an example, see Section 7.2.72, “EndSheetGluingParams”. An example of the tables in this section is provided below.
Note: for the Resource Properties Template below, the italicized text describes the actual text that would be in its place in an actual Resource definition. Cardinality in the Name column of the Resource Structure Template table refers to a cardinality symbol, which is either empty or consists of a symbol, such as “?”. For further details, see Section 1.3.4, “Specification of Cardinality”.
Defines the Resource Class or specifies ResourceElement if the Element only exists as a Resource Subelement.
List of parent Resources that may contain Elements of this type.
List of recommended Partition Keys: For a complete list of Partition Keys, see the description of PartIDKeys in Table 3-27, “Partitionable Resource Element”. Note that Resources may be Partitioned by keys that are not specified in this list.
List of JDF Node types that use the Resource as an Input Resource.
List of JDF Node types that create the Resource as an Output Resource
|
Information about the Element. Note: the “element” data type means that the specified Element must be an in-line Subelement within the Resource. |
||
|
Note: the “refelement” data type means that the specified Element is based on other atomic Resources or Resource Elements. The specified Element must be either an in-line Element or an instance of a ResourceRef Element (see Section 3.10.2, “ResourceRef - Element for Inter-Resource Linking and refelement”). In case of a ResourceRef Element, a “Ref” must be appended to the name specified in the table column entitled “Name”. |
||
|
Information about the FileSpec Resource Note: FileSpec /@ ResourceUsage must match the "someValue" value specified in the parentheses. When a Resource potentially contains multiple FileSpec children, the value of FileSpec @ ResourceUsage distinguishes the FileSpec Resources. |
||
|
Information about the Resource and the Attribute whose value is "someValue" . Note: Some specified Attribute in the specified Resource must match the "someValue" value specified in the parentheses. When a Resource potentially contains multiple children of the same Resource type, the value of some Attribute distinguishes the Resources. |
7.2.2 Address
Definition of an address. The structure is derived from the vCard format and, therefore, is comprised of all address subtypes ( ADR :) of the delivery address of the vCard format. The corresponding XML types of the vCard are quoted in the table.
|
Values include those from: [ISO3166-1:1997] |
||
|
Post office address (vCard: ADR:pobox. For example: P.O. Box 101). |
||
|
Extended address (vCard: ADR:extadd. For example: Suite 245). |
7.2.3 AdhesiveBindingParams
See Section P.4.4, “AdhesiveBindingParams” for details of this deprecated Resource.
7.2.4 ApprovalParams
This Resource provides the details of an Approval Process.
ProofItem , ConventionalPrintingParams , DigitalPrintingParams
|
Minimum number of ApprovalPerson [@ ApprovalRole = "Group" ] whose associated person must sign the ApprovalSuccess for the ApprovalSuccess to be Available . |
||
|
List of people (e.g., a customer, printer or manager) who can sign the approval. |
7.2.4.1 Element: ApprovalPerson
|
If "true" , the person has to sign this approval. In JDF 1.2 and beyond, use ApprovalRole . |
||
|
Role of the ApprovalPerson . Approvinator - The decision of this approver immediately overrides the decisions of the other approvers and ends the approval cycle. The Approvinator need not sign for the approval to become valid. New in JDF 1.3 Group - The approver belongs to a group of which MinApprovals members must sign. Informative - The approver is informed of the Approval Process, but the approval is still valid, even without his approval. |
||
|
Contact (e.g., a customer, printer or manager) who
must
sign the approval. There
must
be a |
7.2.5 ApprovalSuccess
The signed ApprovalSuccess Resource provides the signature that indicates that a Resource has been approved. This is frequently used to model the success of a soft proof, color proof, printing proof or any other sort of proof.
DocIndex , DocRunIndex , RunIndex , RunPage , RunTags, DocTags, PageTags, SetTags, SetIndex, SheetName , Side , SignatureName , TileID
|
Contact * |
List of contacts that have signed off on this approval. Use ApprovalDetails / Contact in JDF 1.3 and above. |
|
|
FileSpec ? |
The file that contains the approval signature. If FileSpec does not exist, ApprovalSuccess is a logical placeholder. Use ApprovalDetails / FileSpec in JDF 1.3 and above. |
7.2.5.1 Element: ApprovalDetails
|
Decision made by the approver specified in this ApprovalDetails / Contact . Approved - approver approved the Resource. ApprovedWithComment - approver approved the Resource but still had some comments. |
||
|
Additional details on the decision made by the approver are specified in this ApprovalDetails / Contact . This value provides additional machine readable details of ApprovalState. Hand written comments and notes may be specified in ApprovalDetails / Comment or ApprovalDetails /@ CommentURL . |
||
|
Contact ? |
||
|
FileSpec ? |
The file that contains the approval signature. If FileSpec does not exist, ApprovalSuccess is a logical placeholder. |
7.2.6 Assembly
Assembly describes how the sections of one or multiple Jobs or Job Parts are bound together.
Component , CutBlock , PageList
Collecting , Gathering , Stripping , WebInlineFinishing
|
Identification of the Assembly if Stripping produces multiple Assembly Elements. |
||
|
Identification of the Assembly Elements if Stripping describes an imposition scheme for multiple Assembly Elements. AssemblyIDs may contain multiple NMTOKENS, when the Assembly Resource specifies an intermediate product that contains multiple final assemblies. |
||
|
Indicates which side is to be bound. BindingSide is ignored when Order = "None" . |
||
|
Identification of the original Job the Assembly belongs to. If not specified, it defaults to the value specified or implied in the JDF Node. |
||
|
JogSide specifies the side on which the AssemblySection Elements will be aligned. |
||
|
Ordering of the individual AssemblySection Elements. Order specifies the topology of the final Assembly . Collecting - The sections are placed within one another. The first section is on the outside. An example is a saddle-stitched brochure. See Section 6.6.10, “Collecting” Gathering - The sections are placed on top of one another. The first section is on the top. An example is a perfect bound magazine. See Section 6.6.20, “Gathering”. None - The sections are not bound. Typically used for flatwork Jobs. List - More complex ordering of the sections. If multiple child AssemblySection Elements are provided, these are gathered on top of one another. The first AssemblySection is on the top. If nested AssemblySection Elements are provided, these are Collected into each other. The first AssemblySection is on the outside. |
||
|
Specifies the physical structure of a newspaper. The structure is based on a broadsheet production. For instance, PhysicalSection = "8 6 8 6" represents a 4 book production with 8 pages in the first physical section, 6 in the second one and so on. |
||
|
Individual AssemblySection Elements which are gathered. AssemblySection Elements must not be specified unless Order = "List" . |
||
|
PageList ? |
Reference to the PageList that describes the pages used in this Assembly . |
|
|
Defines the page sequence for of an Assembly . One PageAssignedList Element corresponds to one or more consecutive Reader Pages. The order of the PageAssignedList Elements specifies the reader order of the assigned pages within the Assembly . PageAssignedList must not be specified if Order = "List" . |
7.2.6.1 Element: AssemblySection
|
Identification of the AssemblySection if Stripping produces a multi-section Assembly . If not specified, it defaults to the value specified or implied in the parent Assembly or AssemblySection . |
||
|
Identification of the AssemblySection Elements if Stripping describes an imposition scheme for a multi-section Assembly . If not specified, it defaults to the value specified or implied in the parent Assembly or AssemblySection . In general AssemblySection /@ AssemblyIDs will contain only a single NMTOKEN value. AssemblyIDs may contain multiple NMTOKENS, when the AssemblySection specifies an intermediate product that contains multiple final products. |
||
|
Identification of the original Job the AssemblySection belongs to. If not specified, it defaults to the value specified or implied in the parent Assembly or AssemblySection . |
||
|
Ordering of the child AssemblySection E lements. Collecting - The child AssemblySection Elements are placed within one another. The first section is on the outside. Gathering - The child AssemblySection Elements are placed on top of one another. The first section is on the top. Deprecation note: starting with JDF 1.4, Sibling AssemblySection Elements are gathered whereas Child AssemblySection Elements are collected. Thus the Relationship of the AssemblySection Elements directly reflects the structure of the Assembly . |
||
|
Additional child AssemblySection Elements which are collected to create this AssemblySection . |
||
|
Defines the page sequence for of an AssemblySection . One PageAssignedList Element corresponds to one or more consecutive Reader Pages. The order of the PageAssignedList Elements specifies the reader order of the assigned pages within the AssemblySection . PageAssignedList must not be specified if child AssemblySection Elements are present in this AssemblySection . |
7.2.6.2 Element: PageAssignedList
PageAssignedList specifies the metadata related to assigned pages.
|
Specifies a broadsheet position within a single Web product. Several PageAssignedList Elements may show the same value for this Attribute, e.g., in a 'tabloid-' or 'magazine production' on a newspaper press. |
||
|
Specifies a logical grouping of page-placement positions from the press managers point of view (see @ PagePlacementName for details). A logical section need not correspond to a physical section. |
||
|
List of the indices of the PageData Elements of the Assembly / PageList specified in this AssemblySection . |
||
|
Specifies the name of a position in a Web product where a Reader Page is placed on a Web Press. In contrast to PageList / PageData /@ PageLabel , PagePlacementName specifies an identifier for a single page on a Web-product level. Therefore, different PagePlacementName values might be assigned to one single PageList / PageData Element. |
Example 7-2: Perfect Bound (Gathering)
Cover wrapped around a perfect bound (gathering) body
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< Assembly BindingSide = "Left" Class = "Parameter" ID = "ASM000" Order = "List"
< AssemblySection AssemblyIDs = "Ass_Cover" >
< AssemblySection AssemblyIDs = "Ass_Body1" />
< AssemblySection AssemblyIDs = "Ass_Body2" />
< AssemblySection AssemblyIDs = "Ass_Insert" />
< AssemblySection AssemblyIDs = "Ass_Body3" />
< AssemblySection AssemblyIDs = "Ass_Body4" />
Example 7-3: Saddle-Stitched Brochure (Collecting)
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< Assembly BindingSide = "Left" Class = "Parameter" ID = "ASM000" Order = "List"
< AssemblySection AssemblyIDs = "Ass_Cover" >
< AssemblySection AssemblyIDs = "Ass_Body1" >
< AssemblySection AssemblyIDs = "Ass_Body2" >
< AssemblySection AssemblyIDs = "Ass_Body3" >
< AssemblySection AssemblyIDs = "Ass_Body4" >
<AssemblyLink Usage="Input" rRef="ASM000"/>
7.2.7 AssetListCreationParams
This Resource provides controls for the AssetListCreation Process.
|
Specifies what type of assets are to be listed. The regular expression represents the MimeType of the assets to be listed. The default behavior is to list everything. In case an asset requires a plug-in or extension in order to be opened in an application, this plug-in or extension should be listed as an asset. |
||
|
Policy that defines which assets must be added to the output RunList . All - List all referenced assets, including those that are unavailable. Available - List all referenced assets, excluding those that are unavailable. |
||
|
FileSpec ( SearchPath ) * |
An ordered list of search paths that indicates where to search for referenced assets if they are not located in the same directory as the input asset. If no FileSpec is specified, the search path is the directory in which the input asset resides and must not be searched recursively. |
7.2.8 AutomatedOverPrintParams
This Resource provides controls for the automated selection of overprinting of black text or graphics. RGBGray2Black and RGBGray2BlackThreshold in ColorSpaceConversion / ColorSpaceConversionOp are used by the ColorSpaceConversion Process in determining the allocation of RGB values to the black ( K ) channel. After the ColorSpaceConversion Process is completed, then the Rendering or Separation Process uses AutomatedOverPrintParams to determine overprint behavior for the previously determined black ( K ) channel.
ElementColorParams , RenderingParams , SeparationControlParams
7.2.9 BarcodeCompParams
BarcodeCompParams specifies the technical compensation parameters for barcodes.
BarcodeReproParams , LayoutElementProductionParams / LayoutElementPart / BarcodeProductionParams
|
The width of the bars is reduced by this amount in micron to compensate for technical spread. |
7.2.10 BarcodeReproParams
BarcodeReproParams specifies the reproduction parameters for barcodes.
BarcodeProductionParams , DeviceMark
|
Indicates the properties of the mask around the graphical content of the barcode that masks out all underlying graphics. None - No masking, barcode is put on top of underlying graphics. WhiteBox - An area of the underlying graphics is masked out (the white box) and the barcode is put on top of this masked area. The area of the white box is the box enclosing all artwork of the barcode, excluding optional human readable text. This would enclose bearer bars, quiet zones and non-optional human readable text (UPC and EAN barcodes.) |
||
|
The Y size in micron of an Element of a 2D barcode e.g., PDF417 . For DATAMATRIX, Y Dimension may be omitted (X Dimension = Y Dimension.). |
||
|
The X size in micron of an Element of a 2D barcode such as DATAMATRIX or PDF417 . |
||
|
the ratio between the width of the narrow bars and the wide bars for those barcodes where ratio the width of the wide bars and narrow bars may vary. |
||
|
Parameters for bar width compensation. The total reduction of bar width is the sum of all BarcodeCompParams /@ CompensationValue . |
7.2.11 BendingParams
BendingParams describes the parameter set for a plate bending and punching Device. A plate is bent and/or punched to fit the press cylinder.
|
If "true" , indicates that the Device must create registration punch holes. |
||
7.2.12 BinderySignature
The BinderySignature is conceptually a folding dummy. It represents multiple pieces of paper, which are folded together in the folder. It is a reusable, size-independent object.
Each BinderySignature consumes a number of Pages from the PageList . If no SignatureCell Elements are specified, each BinderySignature consumes the number of pages as calculated from NumberUp (X*Y*2) or FoldCatalog (The integer value after the F, e.g. F16-x consumes 16 pages). If SignatureCell Elements are specified, the number of pages consumed is the sum of the number of pages for all unique SignatureCell /@ SectionIndex . The number of pages for each SignatureCell /@ SectionIndex is one more than the maximum value of any SignatureCell /@ FrontPages or SignatureCell /@ BackPages for that SignatureCell /@ SectionIndex (it is one more because SignatureCell /@ FrontPages and SignatureCell /@ BackPages begin at zero)
|
The Partition WebName value of the reference web that WebCellAlignment refers to. |
||
|
Specifies the binding edge of this BinderySignature . BindingEdge defines the Spine side the folded BinderySignature . The opposite side defines the Face side. None - The Spine is at the left side of the SignatureCell and the Face is at the right side of the SignatureCell |
||
|
After folding a BinderySignature , the default reference corner is the lower left corner of the BinderySignature . The side coinciding with the last fold is the BindingEdge , the other side of the reference corner the JogEdge . BindingOrientation is the named orientation describing the transformation of the default reference corner to the new reference corner defined by BindingEdge and JogEdge . For BinderySignature Elements defined by FoldCatalog or Fold Elements, the default value of BindingOrientation = "Rotate0" if the folded BinderySignature has a closed head, otherwise BindingOrientation = "Flip0" . For BinderySignature Elements defined by SignatureCell Elements, the default value BindingOrientation = "Rotate0" . For details, see Table 2-4, “Matrices and Orientation values for describing the orientation of a Component” . |
||
|
Describes the type of fold according to the folding catalog in Figure 7-33, “Fold catalog part 1” and Figure 7-34, “Fold catalog part 2”. Value format is: " Fn-i " where “n” is the number of finished pages and “i” is either an integer, which identifies a particular fold or the letter "X" , which identifies a generic fold. E.g., "F6-2" describes a Z-fold of 6 finished pages, and "F6-X . " describes a generic fold with 6 finished pages. Constraint: At least one of SignatureCell , FoldCatalog or Fold must be specified. FoldCatalog must not be specified unless BinderySignatureType = "Fold" . |
||
|
Specification of the orientation applied to the substrate of all stacked webs before applying folding (only specified at root BinderySignature node, and would default to Rotate0). |
||
|
Specifies the JogEdge of the folded BinderySignature . The JogEdge defines the Head side of the folded BinderySignature . The opposite side defines the Foot side. None - The Head side is the top of the SignatureCell , the Foot side is the bottom of the SignatureCell . |
||
|
Specifies a regular, multi-up grid of SignatureCell Elements into which content pages are mapped. The first value specifies the number of columns of SignatureCell Elements, and the second value specifies the number of rows of SignatureCell Elements in the multi-up grid (both numbers are integers). When the BinderySignature is Partitioned (e.g., by WebName ), NumberUp may be different from leaf to leaf. |
||
|
If BinderySignatureType is "Grid" , this boolean defines whether the outside margins of strip cells have to be taken into account. E.g., if OutsideGutter is false , the Spine ( S2 ) of the strip cells at the left border of the grid is considered to be 0. |
||
|
A list of doubles describing the staggering for subsequent columns. The number of entries in the list describes the periodicity of the staggering. Each value gives a factor of the strip cell height ((y value of TrimSize ) + TrimHead + TrimFoot ) by which to shift the corresponding column (can be negative). E.g., StaggerColumns = "0.0 0.333 0.666" specifies to shift each This Element may be present when BinderySignatureType = "Grid" . At most one of StaggerColumns or StaggerRows must be specified. |
||
|
Indicates if the BinderySignature has to be considered as a continuous repetition for staggering. This Attribute must not be present unless exactly one of StaggerRows or StaggerColumns is specified. Consider a grid with m columns and n rows with StaggerContinuous = "true" . If StaggerColumns is specified, the BinderySignature must be considered continuous with a height H equal to n multiplied by the strip cell height. If StaggerColumns has a value of y for a certain column, that column is shifted up (assuming y > 0) by an amount equal to y multiplied by the strip cell height (in the same way as described for StaggerColumns ). All content (even partial cells) that falls above H (the top of BinderySignature ) is shifted to the bottom such that the top of the shifted content is just below the original bottom cell in the column. For example, if y is 0.666, then the top 66.6% of the top cell is shifted to be just below the original bottom cell. Analogous for StaggerRows . |
||
|
A list of doubles describing the staggering for subsequent rows. The number of entries in the list describes the periodicity of the staggering. Each value gives a factor of the strip cell width ((x value of TrimSize ) + TrimFace + Spine ) by which to shift the corresponding row (can be negative). E.g., "0.0 0.333 0.666" specifies to shift each This Element may be present when BinderySignatureType = "Grid" . At most one of StaggerColumns or StaggerRows must be specified. |
||
|
Zero based SignatureCell index (coordinate) that the bottom left SignatureCell in this web is aligned with in the full web (only specified at the WebName Partition, and would default to " 0 0 " ). See Figure 7-4, “WebCellAlignment, Example 1”, Figure 7-5, “WebCellAlignment Example 2” and Figure 7-6, “WebCellAlignment Example 3”. Also, the “stacking” of the webs is implied by the order of the webs within the BinderySignature . The back side of a WebName Partition of a BinderySignature will be touching the front side of the WebName partition of the BinderySignature that follows it in the JDF file. |
||
|
The layout as defined by a pre-existing die. DieLayout must be present when BinderySignatureType = "Die" . |
||
|
Fold * |
Describes the folding operations in the sequence in which they are to be carried out. When both Fold and FoldCatalog are specified, FoldCatalog defines the topology of the folding scheme, and the specifics of each individual fold are described by the Fold Elements. The Fold Elements have precedence. Fold must not be specified if SignatureCell Elements are present. Fold must not be specified unless BinderySignatureType = "Fold" . |
|
|
Describes the SignatureCell Elements used in this BinderySignature . SignatureCell Elements are ordered in X-Y direction starting at the lower left-hand corner of the BinderySignature . When both SignatureCell and FoldCatalog are specified, FoldCatalog defines the topology of the folding scheme, and the specifics of each individual Signature cell are described by the SignatureCell Elements. The SignatureCell Elements must have precedence. SignatureCell must not be specified if Fold Elements are present. |
|
|
|
Example 7-4: Pseudo Code to Generate Page Count from SignatureCell Elements
for sc in BinderySignature/SignatureCell
if ( si > maxSectionIndexSeen)
for index from maxSectionIndexSeen to si - 1:
maxSectionPages[si] = max(maxSectionPages[si],page)
maxSectionPages[si] = max(maxSectionPages[si],page)
for sectionIndex from 0 to maxSectionIndexSeen
totalPages += 1 + maxSectionPages[sectionIndex]
7.2.12.1 Element: SignatureCell
SignatureCell Elements describe a set of individual page cells in a BinderySignature .
Note: “Page number” in the table below refers to finished pages from the PageList numbered from 0 to n, as opposed to Folio pages, which are the numbers that appear in print with the content of the document; the difference being that pages without Folio numbering are counted. As the BinderySignature is a reusable object, the page numbers refer to finished pages numbered from 0 to n as if this BinderySignature were the only section of the Assembly . The consuming Device needs to calculate the final product page number using the Assembly and StrippingParams /@ SectionList . The BinderySignature cells must not contain final page numbers unless Assembly /@ Order = "None" .
|
Page numbers for the back finished pages forming a foldout. Deprecation note: starting with JDF 1.4, use FaceCells to describe foldouts. |
||
|
Page numbers of the back finished pages of a SignatureCell . The number of entries in FrontPages and BackPages must be identical. The entries with an identical index in FrontPages and BackPages are back-to-back in the layout. If not specified, the layout is one-sided. |
||
|
Indicates the bottle angle, which is the slight rotation of the SignatureCell needed to compensate for the rotation fault introduced when making cross-folds. |
||
|
List of indices of SignatureCell Elements that form a foldout together with this SignatureCell . The SignatureCell that contains FaceCells is the parent of the foldout, typically the Page that is attached to the spine. Details of each foldout Page are described by a SignatureCell Element. |
||
|
Page numbers for the front finished pages forming a foldout. Deprecation note: starting with JDF 1.4, use FaceCells to describe foldouts. |
||
|
Page numbers of the front finished pages of a SignatureCell . Multiple page cells with the same properties except for the finished pages to which they are assigned may be summarized as one SignatureCell with multiple entries in FrontPages . |
||
|
Indicates the orientation of the SignatureCell . Left - 90˚ counter-clockwise rotation. New in JDF 1.3 |
||
|
Unique logical index of the page section that are to fill this SignatureCell . This is an indirect logical index. The actual section index is defined in StrippingParams /@ SectionList . |
||
|
The name of the 1-up station in the die layout. Constraint: if BinderySignature /@BinderySignatureType = "Die" , this Element should be specified. Constraint: if BinderySignature /@BinderySignatureType = "Die" and BinderySignature / DieLayout contains more than 1 Station , this Attribute must be specified. |
Example 7-5: StrippingParams: Foldout Using FaceCells
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<!--Stripping Foldout example corresponding to spec example n.6.5 - with new
< StrippingParams Class = "Parameter" ID = "r000005"
PartIDKeys = "CellIndex" Status = "Available" >
< BinderySignatureRef rRef = "r000006" />
< StrippingParams CellIndex = "0" >
<!--stripcell for the folded out foldout(front page=4)-->
< StripCellParams TrimSize = "200 400" />
< StrippingParams CellIndex = "1" >
<!--stripcell for the inner page of the foldout foldout(front page=5)-->
< StripCellParams TrimSize = "300 400" />
< StrippingParams CellIndex = "2" >
<!--stripcell for the inner page of the foldout foldout(front page=0)-->
< StripCellParams TrimSize = "320 400" />
< BinderySignature Class = "Parameter" ID = "r000006" Status = "Available" >
<!--this is the foldout foldout cell-->
< SignatureCell BackPages = "3" FrontPages = "4" />
<!--this cell is the inner page of the foldout, i.e. the page that is
attached to the spine The new attribute FaceCells refers to the cell(s)
that describe the foldout; in this case the cell to the left. The front
and back pages of the foldout are listed in the respective cell(s)
< SignatureCell BackPages = "2" FaceCells = "0" FrontPages = "5" />
<!--this is the cell that has no foldout-->
< SignatureCell BackPages = "1" FrontPages = "0" />
<StrippingParamsLink Usage="Input" rRef="r000005"/>
7.2.13 BlockPreparationParams
This Resource describes the settings of a BlockPreparation Process. For the tightbacking there are four different kinds of book forms as shown in Figure 7-7.
|
|
|
|
For the rounding and for the backing there are two additional measurement as shown in Figure 7-8.
|
|
|
Description of the register ribbons that are included within the book block. |
7.2.14 BoxFoldingParams
This Resource defines the parameters for folding and gluing blanks to folded flat boxes in a box folder-gluer Device.
|
X position of folds for an unfolded box beginning from the origin of the coordinate system (left side) increasing from minimum to maximum (expressed in points). See Figure 7-10, “BoxFoldingType Attribute for values of Type00, Type01 and Type02” through Figure 7-13, “BoxFoldingType Attribute for values of Type15 and Type20”. The first value of BlankDimensionsX is the position of the fold marked by X0 in a diagram, e.g., Figure 7-10. The second value of BlankDimensionsX is the position of the fold marked by X1, and so on. BlankDimensionsX must not be specified unless BoxFoldingType is also specified. |
||
|
Y position of folds for of an unfolded box beginning from the origin of the coordinate system (bottom side) increasing from minimum to maximum (expressed in points). See Figure 7-10, “BoxFoldingType Attribute for values of Type00, Type01 and Type02” through Figure 7-13, “BoxFoldingType Attribute for values of Type15 and Type20”. The first value of BlankDimensionsY is the position of the fold marked by Y0 in a diagram, e.g., Figure 7-10. The second value of BlankDimensionsY is the position of the fold marked by Y2, and so on. BlankDimensionsY must not be specified unless BoxFoldingType is also present. |
||
|
Basic predefined folding types. See the drawings referenced from each defined value below. Each drawing is shown from the print side with the lid at the top. Each type is described with a sequence of BoxFoldAction Elements. The most common sequences (folding types) are predefined, All other are 'special' and must be described in detail. Type00 - Special type for boxes that are not pre-defined. See Figure 7-10. Type01 - see Figure 7-10. Type02 - see Figure 7-10. Type03 - see Figure 7-11. Type04 - see Figure 7-11. Type10 - see Figure 7-11. Type11 - see Figure 7-12. Type12 - see Figure 7-12. Type13 - see Figure 7-12. Type15 - see Figure 7-13. Type20 - see Figure 7-13. |
||
|
Application work step in a Box folder-gluer. The sequence of BoxFoldAction , BoxApplication and GlueLine Elements defines the sequence of work steps. The first Element is applied first. Application SHOULD be described with a combined Inserting process. Deprecation note: starting with JDF 1.4, a Combined Process that includes the BoxFolding and Inserting Processes replaces BoxApplication . |
||
|
Individual work step in a Box folder-gluer. The sequence of BoxFoldAction , BoxApplication and GlueLine Elements defines the sequence of work steps. The first Element is applied first. |
||
|
GlueLine * |
Specification of a glue line. The GlueLine is applied to the blank in the coordinate system of the folder gluer at the state after all prior BoxFoldAction and BoxApplication Elements have been applied. The sequence of BoxFoldAction , BoxApplication and GlueLine Elements defines the sequence of work steps. The first Element is applied first. |
7.2.14.1 Element: BoxApplication
A BoxApplication describes the application of an external Component such as a window or handle to a folding box in the box folder-gluer. Note that a short description of the application should be specified in BoxApplication / @DescriptiveName . Application of an external Component SHOULD be described with a combined Inserting process.
|
Area in the current coordinate system of the folder gluer where the Component is applied. Note: A single point is specified by X0 = X1 and Y0 = Y1 of the rectangle and a line is specified by X0 = X1 or Y0 = Y1. |
||
|
Reference to a Component that is applied. This Component must also be specified as in input Component to the BoxFolding Process with ProcessUsage = "Application" |
||
|
GlueLine * |
Specification of a glue lines needed to glue the Component described in this BoxApplication . The glue lines are applied to the Component in the coordinate system of the BoxApplication / Component . The glue lines applied to the blank are specified in BoxFoldingParams / GlueLine . |
7.2.14.2 Element: BoxFoldAction
BoxFoldAction describes an action in the folder-gluer that is perpendicular or diagonal to the movement path of the blank.
|
Identification of the upper right corner of the flap or fold that is affected by this BoxFoldAction . The first value of the XYPair refers to an indexed fold in BlankDimensionsX ; the second value of the XYPair refers to an indexed fold in BlankDimensionsY. If either X or Y spans multiple flaps, it must be set to -1. |
||
|
Individual Action in the folder gluer. Values are from: Table 7-82, “Action Attribute Values”. |
||
|
GlueLine * |
Specification of a glue lines needed to glue the Component described in this BoxApplication . The GlueLine s are applied to the Component in the coordinate system of the BoxApplication / Component . The GlueLine s applied to the blank are specified in BoxFoldingParams / GlueLine . |
-- Attribute: Action
|
For a drawing, see Figure 7-9, “Folding examples for some values of BoxFoldAction/@Action”. |
|
|
For a drawing, see Figure 7-9, “Folding examples for some values of BoxFoldAction/@Action”. |
|
|
For a drawing, see Figure 7-9, “Folding examples for some values of BoxFoldAction/@Action”. |
|
|
For a drawing, see Figure 7-9, “Folding examples for some values of BoxFoldAction/@Action”. |
|
|
For a drawing, see Figure 7-9, “Folding examples for some values of BoxFoldAction/@Action”. |
|
|
A ReverseFold is topologically equivalent to FrontFoldDiagonal but uses different equipment with other restrictions on Media weight and size and is therefore specified individually. For a drawing, see Figure 7-9, “Folding examples for some values of BoxFoldAction/@Action”. |
|
Example 7-6: BoxFoldingParams/BoxFoldAction
For instance, processing a Type01 blank (Figure 7-10, “BoxFoldingType Attribute for values of Type00, Type01 and Type02”) has the following actions:
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< BoxFoldingParams Class = "Parameter" ID = "BFP000" Status = "Available" >
< BoxFoldAction FoldIndex = "0 -1" Action = "LongPreFoldLeftToRight" />
< BoxFoldAction FoldIndex = "2 -1" Action = "LongPreFoldRightToLeft" />
< BoxFoldAction FoldIndex = "1 -1" Action = "LongFoldLeftToRight" />
< BoxFoldAction FoldIndex = "3 -1" Action = "LongFoldRightToLeft" />
<BoxFoldingParamsLink Usage="Input" rRef="BFP000"/>
|
|
|
|
|
|
Dimensions and Actions for below Figures:
|
|
|
|
Individual shape with customer defined dimensions and actions |
||
|
|
|
|
|
|
|
|
|
7.2.15 BoxPackingParams
This Resource defines the parameters for packing a box of components. Details of the box used for BoxPacking can be found in the Component ( Box ) Resource that is also an input of the BoxPacking Process.
|
Component s per row in the shipping box, as illustrated by A in Figure 7-14 . If the Component s represent Bundle s, the number of Bundle s is specified. |
||
|
Columns per shipping box. Columns are in the 3rd Dimension in Figure 7-14 , and are thus not illustrated. |
||
|
Defines the coordinate pair that is facing the bottom of the box, defining the horizontal plane. |
||
|
Number of copies in the box. Copies MUST NOT be specified if MaxWeight is present. |
||
|
Material to fill boxes that are not completely filled, as illustrated by F in Figure 7-14 . Any - Explicit request for system specified filling. |
||
|
Layers per shipping box, as illustrated by L in Figure 7-14 . |
||
|
Maximum weight of a packed box in grams. MaxWeight MUST NOT be specified if Copies is present. |
||
|
Name of the box packing pattern. Used to store a predefined pattern that defines the layers and positioning of individual component in the box or carton. |
||
|
Rows per shipping box, as illustrated by R in Figure 7-14 . |
||
|
Number of tie Sheets at each row. The first value is outside the first row, the next value between the first and second row and so forth. If more rows than values are specified, counting restarts at the 0 position. If fewer layers than values are specified, all tie Sheets that are not adjacent to a row are ignored. |
||
|
Number of underlay Sheets at each layer, as illustrated by U in Figure 7-14 . The first value is underneath the bottom layer, the next value above the first layer and so forth. If more layers than values are specified, counting restarts at the 0 position. If less layers than values are specified, all underlay Sheets that are not adjacent to a layer are ignored. |
|
7.2.16 BufferParams
This Resource provides controls for Buffer Process.
|
Minimum amount of time that an individual Resource must be buffered. |
7.2.17 Bundle
Bundles are used to describe various kinds of sets of Component s. Note that Bundle Resources can be created by many press or postpress Processes and not only Bundling .
|
BoundSet - Stack of components that are bound together. CollectedStack - Components collected on a saddle, result of Collecting Process CompensatedStack - Loose stack of compensated components Roll - Rolled components on a print Roll. Sheet - Multiple individual items printed onto one Sheet. Stack - Loose stack of equally stacked components. StrappedStack - Strapped stack of equally stacked components. StrappedCompensatedStack - Strapped stack of compensated components. |
||
|
Total amount of individual finished pages that this bundle contains. If not specified, it must be calculated from the individual BundleItem Elements. |
||
|
Total amount of individual Reader Pages that this bundle contains. If not specified, it must be calculated from the individual BundleItem Elements. |
||
|
Total amount of individual products that this bundle contains. If the bundle contains one or more Component [contains ( @ComponentType , "FinalProduct" )], TotalAmount refers to the number of final products. Note that this is neither always the next level of BundleItem nor the lowest level of BundleItem. For instance, the next level may be the boxes in a carton, whereas the lowest level may be the Sheets comprising the brochure. The correct number in this example would be the number of Brochures. If not specified, it must be calculated from the individual BundleItem Elements. |
||
|
References to the individual items that form this Bundle . |
7.2.17.1 Element: BundleItem
A Bundle is described as a set of BundleItem Elements. Since BundleItem Elements reference Component Resources which themselves can reference further Bundle Resources, the structure is recursive.
|
Name of the bundle item. Used for referencing individual BundleItem Elements in a Bundle . |
||
|
Named Orientation of the Component respective to the Bundle coordinate system. For details, see Table 2-4, “Matrices and Orientation values for describing the orientation of a Component”. At most one of Orientation or Transformation must be specified. |
||
|
Orientation of the Component respective to the Bundle coordinate system. At most one of Orientation or Transformation must be specified. |
||
Example 7-7: Bundle: Boxing and Palletizing
The following example code shows a JDF that describes boxing and palletizing for 4200 books. The appropriate Bundle Elements have orange tags and magenta Attributes. The Resources have not yet been completely filled in.
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID = "Bundle" Status = "Waiting"
Type = "ProcessGroup" JobPartID = "ID20" Version = "1.4" >
<!-- The BoxPacking Process consumes the thing to pack and the boxes-->
<!-- The BoxPacking Process creates packed boxes -->
< JDF ID = "n0235" Status = "Waiting" Type = "BoxPacking" JobPartID = "ID21" >
< ComponentLink ProcessUsage = "Box" Usage = "Input" rRef = "BoxID" />
< BoxPackingParamsLink Usage = "Input" rRef = "BoxParamsID" />
< ComponentLink Usage = "Input" rRef = "ComponentID" />
< ComponentLink Usage = "Output" rRef = "PackedBoxID" />
<!-- The BoxPacking Process has the following local resources -->
< BoxPackingParams Class = "Parameter" ID = "BoxParamsID"
< Component Amount = "100" Class = "Quantity" ID = "BoxID"
Status = "Available" ComponentType = "Sheet" />
<!-- This Component describes a Box with 42 Books -->
< Component Amount = "100" Class = "Quantity" ID = "PackedBoxID"
Status = "Unavailable" ComponentType = "Sheet" >
< Bundle BundleType = "Box" TotalAmount = "42" >
< ComponentRef rRef = "ComponentID" />
< Component Amount = "4200" Class = "Quantity" ID = "ComponentID"
Status = "Available" ComponentType = "Sheet" />
<!-- This Component describes the contents of the pallet: 100
< Component Amount = "10" Class = "Quantity" ID = "palletContentsID"
Status = "Unavailable" ComponentType = "Sheet" >
< Bundle BundleType = "Pallet" TotalAmount = "420" >
< ComponentRef rRef = "PackedBoxID" />
< JDF ID = "n0239" Status = "Waiting" Type = "Palletizing" JobPartID = "ID22" >
< ComponentLink Usage = "Input" rRef = "PackedBoxID" />
< PalletLink Usage = "Input" rRef = "palletID" />
< PalletizingParamsLink Usage = "Input" rRef = "palletParamsID" />
< ComponentLink Usage = "Output" rRef = "palletContentsID" />
< Pallet Amount = "10" Class = "Consumable" ID = "palletID"
Status = "Available" PalletType = "Euro800x600" />
< PalletizingParams Class = "Parameter" ID = "palletParamsID"
7.2.18 BundlingParams
BundlingParams describes the details of a Bundling Process.
|
Number of copies within a bundle. Copies must not be specified if Length is present. |
||
|
Length of a bundle. Length must not be specified if Copies is present. |
|
7.2.19 ByteMap
This Resource specifies the structure of bytemaps produced by various Processes within a JDF system. A ByteMap represents a raster of image data. This data may have multiple bits per pixel, may represent a varying set of color planes, and may be interleaved. A Bitmap is a special case of a ByteMap in which each pixel is represented by a single bit per color.
Personalized printing requires that certain regions of a given page be dynamically replaced. The optional mask associated with each band of data allows for omitting certain pixels from the base image represented by the ByteMap so that they can be replaced.
|
Identifies the precedence given when ordering the produced bands. BandOrdering is required for non-interleaved data and must be ignored for interleaved data if specified. BandMajor - The position of the bands on the page is prioritized over the color. ColorMajor - All bands of a single color are played in order before progressing to the next plane. This is only possible with non-interleaved data. |
||
|
Values are from: Table 7-254, “ElementType Attribute Values”. Note: values are the same as LayoutElement @ ElementType . |
||
|
Height of the overall image that may be broken into multiple bands. Modification note: starting with JDF 1.4, FrameHeight is optional. |
||
|
Width of overall image that may be broken into multiple columns. Modification note: starting with JDF 1.4, FrameWidth is optional. |
||
|
Indicates whether or not the data has been halftoned. Modification note: starting with JDF 1.4, Halftoned is optional. |
||
|
If "true" , the data are interleaved or chunky. Otherwise the data are non-interleaved or planar. Modification note: starting with JDF 1.4, Interleaved is optional. |
||
|
Modification note: starting with JDF 1.4, Resolution is optional. |
||
|
Band * |
Array of bands containing raster data. Modification note: starting with JDF 1.4, Band is optional. |
|
|
Details of the colors represented in this ByteMap . |
||
|
A FileSpec Resource pointing to a location where the raster is stored or is be stored shortly |
||
|
Ordered list containing information about which colorants are represented and how many bits per pixel are used. Modification note: starting with JDF 1.4, PixelColorant is optional. |
7.2.19.1 Element: Band
7.2.20 CaseMakingParams
This Resource describes the settings of a CaseMaking Process.
|
|
Defines the width of the part of the CoverMaterial on the lower edge inside of the case. If not specified, defaults to TopFoldIn . |
|||
|
Method of wrapping the corners of the cover material around the corners of the board. |
|||
|
Defines the width of the part of the cover material on the front edges inside of the case. |
|||
|
Width of the joint as seen when laying the cardboard on the cover material, in points. |
|||
|
Defines the width of the cover material on the top edge inside of the case. |
|||
|
GlueLine ? |
Because the glue is applied to the whole back side of the cover material, GlueLine /@ AreaGlue must be set to "true" . |
||
7.2.21 CasingInParams
This Resource describes the settings of a CasingIn Process. The geometry is always centered See Figure 7-17.
|
|
Inner radius of the case spine rounding. If not specified, no rounding of the case spine is performed. |
||
|
GlueLine + |
Deprecation note: starting with JDF 1.4, use GlueApplication . |
7.2.22 ChannelBindingParams
This Resource describes the details of the ChannelBinding Process.
Figure 7-18 depicts the ChannelBinding Process.
|
The symbols W , L and ClampD of Figure 7-18 are described by the Attributes ClampD and ClampSize of the table below.
|
The name of the clamp (or preassembled cover with clamp) manufacturer and the name of the specific item. |
||
|
Determines the color of the clamp/cover. If ClampSystem = "true" , then the color of the cover is also meant. |
||
|
A more specific, specialized or site-defined name for the color. If ClampColorDetails is supplied, ClampColor SHOULD also be supplied. |
||
|
The distance of the clamp that was “pressed away” (see Figure 7-18 Parameters used for channel binding). |
||
|
The shape size of the clamp. The first number of the shape data type corresponds to the clamp width W (see Figure 7-18 ) which is determined by the final height of the block of Sheets to be bound. The second number corresponds to the length L (see Figure 7-18). The third corresponds to the spine length (not visible in Figure 7-18). The spine length is perpendicular on the paper plane. |
||
7.2.23 CIELABMeasuringField
Information about a color measuring field. The color is specified as CIE-L*a*b* value.
ColorControlStrip , Layout / MarkObject
|
Position of the center of the color measuring field in the coordinates of the MarkObject that contains this mark. If the measuring field is defined within a ColorControlStrip , Center refers to the rectangle defined by Center and Size of the ColorControlStrip . |
||
|
Density filter standard used during density measurements. Deprecation note: starting with JDF 1.1, use ColorMeasurementConditions / @DensityStandard . |
||
|
Observer in degree (2 or 10). In JDF 1.1 and beyond, use ColorMeasurementConditions /@ Observer |
||
|
Percentage values for each separation. The number of array Elements must match the number of separations. |
||
|
Screen ruling values in lines per inch for each separation. The number of array Elements must match the number of separations. |
||
|
Description of measurement setup. Deprecation note: starting with JDF 1.1, use details from ColorMeasurementConditions |
||
|
Detailed description of the measurement conditions for color measurements. |
7.2.24 CoilBindingParams
This Resource describes the details of the CoilBinding Process.
|
The name of the coil manufacturer and the name of the specific item. |
||
|
A more specific, specialized or site-defined name for the color. If ColorDetails is supplied, Color SHOULD also be supplied. |
||
|
The coil diameter to be produced is determined by the height of the block of Sheets to be bound. |
||
|
Amount of vertical shift that occurs as a result of the coil action while opening the document. It is determined by the distance between the holes. In JDF 1.2 and beyond, use the value implied by HoleMakingParams /@ HoleType . |
||
|
Details of the holes in CoilBinding . |
7.2.25 CollectingParams
The Collecting Process needs no special Attributes. However, this Resource is provided as a container for extensions of the Collecting Process.
|
7.2.26 Color
Color describes spot color inks, process color inks and any other coating, for instance varnish or gloss coating. Spot colors are named colors that can either be separated or converted to process colors. It is important to know the neutral density of the colorant for trapping and, in many cases, the Lab values for representing them on screen. If you know the Lab value, you can calculate the neutral density. When representing colors on screen, a conversion to process colors must be defined. This conversion is a simple linear interpolation between the CMYK value of the 100% spot color and its tint.
A color is represented by a Color Element. It has a required Name Attribute, which represents the name of either a spot color or a process color. When ColorantAlias has been used in ElementColorParams and/or in ColorantControl to clean up string names of spot colors, the resolved, not the uncorrected duplicate, ColorantAlias /@ ReplacementColorantName spot color name must match Color /@ Name . The four names that are reserved for representing process CMYK color names are Cyan , Magenta , Yellow and Black . Every colorant can have a Lab and/or CMYK color value. If both are specified and a system is capable of interpreting both values, the Lab value overrides the CMYK definition, unless the target Device is compatible with CMYK, (i.e., ColorantControl /@ ProcessColorModel = "DeviceCMYK" ). In this case the CMYK value has precedence.
The Lab value represents the L, a, b readings of the ink on certain media. This means that spot inks printed on three different kinds of stocks have different Lab values. Pantone books, for example, provide Lab values for three kinds of paper: coated (not necessarily glossy), matte and uncoated . Thus a color of ink should identify the media for which the Color is specified. CMYK colors are used to approximate spot colors when they are not separated. This conversion can be done by a color management system, or there can be fixed CMYK representation defined by color books such as Pantone.
ColorPool , LayoutPreparationParams / PageCell
|
Actual name of the color in the PDL. ActualColorName SHOULD be used to identify the color. If not specified, defaults to the value of @ Name . |
||
|
CMYK value of the 100% tint value of the colorant. Although optional , it is highly recommended that this value be filled when the colorant is a spot colorant, (i.e., not part of the ProcessColorModel ). This preferred CMYK may be associated with an ICC source profile defined in the FileSpec Resource with a ResourceUsage = "ColorProfile" when the target CMYK is different from the PDL CMYK. |
||
|
Definition of the color identification book name that is used to represent this color. The color book name must match the name defined by the color book vendor CIP4 ColorBook Uncoated Grade 5 PANTONE C - an example PlaceHolder - PlaceHolder is a special token that indicates that the Color / @Name is not a real color but a place holder like 'Spot1' that MUST be resolved when the content arrives. Added in JDF 1.3 Modification note: starting with JDF 1.2, the data type changes from NMTOKEN to string. |
||
|
Definition of the Color within the standard specified by ColorBook . This entry must exactly match the color book entry as defined by the ColorBook specified vendor, including capitalization and media type extension. When using ICC Profiles, this maps to the NCL2 value of a namedColorType tag of an ICC color profile. This entry is used to map from the JDF Color to an ICC namedColorType tag. |
||
|
Definition of the name prefix of the color book entry within a named ICC profile. This entry is used to map from the JDF Color to an ICC namedColorType tag. |
||
|
Definition of the name suffix of the color book entry within a named ICC profile. This entry is used to map from the JDF Color to an ICC namedColorType tag. |
||
|
Mapping to a color name. Allowed values are defined in Section A.3.3.3, “NamedColor”. |
||
|
A more specific, specialized or site-defined name for the color. If ColorDetails is supplied, Color SHOULD also be supplied. |
||
|
A name that characterizes the colorant. DieLine - Marks made with colorants of this type are ignored for trapping. Trapping Processes need not generate a color plane for this colorant. DieLine can be used for auxiliary process separations. DieLine marks will generally appear on proof output but will not be marked on final output, (e.g., plates). Note that the ColorantControl Resource must be correctly set up for the RIP and that ColorType = "DieLine" does not implicitly remove the DieLine separation from final output. Normal - Marks made with colorants of this type, marks covered by colorants of this type, and marks on top of colorants of this type are trapped. Transparent - Marks made with colorants of this type are to be ignored for trapping. Trapping Processes are not to generate a color plane for this colorant. This value should be used for varnish. Opaque - Marks covered by colorants of this type are ignored for trapping. Opaque can be used for metallic inks. OpaqueIgnore - Marks made with colorants of this type and marks covered by colorants of this type are ignored for trapping. OpaqueIgnore can be used for metallic inks. |
||
|
Density value of colorant (100% tint). Whereas NeutralDensity describes measurements of inks on substrate with wide-band filter functions, Density is derived from measurements of inks on substrate with special small-band filter functions according to ANSI and DIN. |
||
|
Gray value of the 100% tint value of the colorant. Although OPTIONAL, it is highly RECOMMENDED that this value be filled when the colorant is a spot colorant, MappingSelection = "UseProcessColorValues" and ColorantControl /@ ProcessColorModel = "DeviceGray" . Uses a subtractive color model: 0.0 means 100% coverage with colorant, while 1.0 means no coverage. |
||
|
This value specifies the mapping method to be used for this Color. MappingSelection can be specifically used to indicate how a combination of process colorant values will be obtained for any spot color when the separation spot colorant itself is not to be used. UsePDLValues - Use color values specified in the PDL for this color. See [ColorPS] . UseLocalPrinterValues - Use the Printer’s best local mapping for this Color . UseProcessColorValues - Use the values defined in this Color . |
||
|
Coated - Pertains to gloss coated. |
||
|
Name of the colorant. This is the value that must match the Name Attribute of a SeparationSpec that references this color, (e.g., in ColorantControl / DeviceNSpace / SeparationSpec /@ Name or ColorantControl / ColorantParams / SeparationSpec /@ Name ). This Name Attribute may also be referenced from the Name Attribute in the Ink Resource. Name may also be referenced from ColorantAlias /@ ReplacementColorantName . Only one Color with any given Name must be specified in a ColorPool . |
||
|
A number in the range of 0.001 to 10 that represents the neutral density of the colorant, defined as 10*log(1/Y) . Y is the tristimulus value in CIEXYZ coordinates, normalized to 1.0. |
||
|
Representation of the original 8-bit byte stream of the Color Name . Used to transport the original byte representation of a Color Name when moving JDF tickets between computers with different locales. Only one Color with any given RawName must be specified in a ColorPool . |
||
|
If "true" , the alternate color space definition defined in the PDL must be used for color space transformations when available. If "false" , the alternate color space definitions defined in sRGB , CMYK or DeviceNColor of this Color must be used depending on the value of ColorantControl /@ ProcessColorModel . In JDF 1.2 and beyond, use MappingSelection . |
||
|
Detailed description of the measurement conditions for color measurements. |
||
|
Elements that define the colorant in a non-standard Device-dependent process color space. DeviceNColor can be specified when Name is a spot colorant (not one of the DeviceNSpace colorants) and ColorantControl /@ ProcessColorModel = "DeviceN" . |
||
|
FileSpec ( ColorProfile ) ? |
A FileSpec Resource pointing to an ICC named color profile that describes further details of the color. This ICC profile is intended as a source profile for the named color whose equivalent CMYK value is given in the CMYK Attribute. |
|
|
FileSpec ( TargetProfile ) ? |
A FileSpec Resource pointing to an ICC profile that defines the target output Device in case the object that uses the Color has been color space converted to a Device color space. FileSpec ( TargetProfile ) applies to the alternate color defined by the value of MappingSelection . |
|
|
Description of the printing condition specific color properties of a colorant, (i.e., how is the printed color result specific to media, screening, etc.). |
||
|
A list of color transfer functions that is used to convert a tint value to one of the alternative color spaces. The transfer functions that are not specified here default to a linear transfer: "0 0 1 1" . |
7.2.26.1 Element: DeviceNColor
|
Value of the 100% tint value of the colorant in the ordered DeviceN space. The list must have N Elements. A value of 0 specifies no ink and a value of 1 specifies full ink. The mapping of indices to colors is specified in the DeviceNSpace Element of the ColorantControl Resource. |
||
|
Color space name, (e.g., HexaChrome or HiFi). Name must match ColorantControl / DeviceNSpace /@ Name . |
7.2.26.2 Element: PrintConditionColor
The PrintConditionColor Element describes the specific properties of a colorant (named in Color / @Name ) when applied in a given printing condition, (i.e., media surface, media opacity, media color, screening/RIP, (e.g., halftone) technology). It is used to overwrite the generic values of Color , which are supplied as the default. See the descriptions in Color for details of the individual Attributes and Elements.
|
CMYK of the PrintConditionColor . Default value is from: parent Color / @CMYK |
||
|
ColorBook of the PrintConditionColor . Default value is from: parent Color / @ColorBook |
||
|
ColorBookEntry of the PrintConditionColor . Default value is from: parent Color / @ColorBookEntry |
||
|
ColorBookPrefix of the PrintConditionColor . Default value is from: parent Color / @ColorBookPrefix |
||
|
ColorBookSuffix of the PrintConditionColor . Default value is from: parent Color / @ColorBookSuffix |
||
|
Density of the PrintConditionColor . Default value is from: parent Color / @Density |
||
|
Lab of the PrintConditionColor . Default value is from: parent Color / @Lab |
||
|
This value specified the mapping method to be used for this Color. Default value is from: parent Color / @MappingSelection . UsePDLValues - Use color values specified in the PDL for this color. See [ColorPS] . UseLocalPrinterValues - Use the Printer's best local mapping for this Color . UseProcessColorValues - Use the values defined in this Color . |
||
|
Media front and back surfaces can be different, affecting color results. If the Media / @FrontCoatings , Media / @BackCoatings or Media / @Gloss Attributes indicate differences in surface then MediaSide can be used to specify the side of the media to which the PrintConditionColor Attributes pertain. |
||
|
NeutralDensity of the PrintConditionColor . Default value is from: parent Color / @NeutralDensity |
||
|
PrintConditionName specifies a particular screening condition and printing condition that this PrintConditionColor Element applies to. In order to map a PrintCondition with a PrintConditionColor , PrintConditionName must match PrintCondition /@ Name . If not specified, this PrintConditionColor matches all PrintCondition but may still be dependent on Media . |
||
|
sRGB of the PrintConditionColor . If not specified, defaults to the parent Color / @sRGB . |
||
|
DeviceNColor of the PrintConditionColor . If not specified, defaults to the parent Color / @ DeviceNColor . |
||
|
FileSpec ( TargetProfile ) |
FileSpec ( TargetProfile ) of the PrintConditionColor . If not specified, defaults to the parent Color / FileSpec ( TargetProfile ) |
|
|
Media * |
Specifies one or more Media that this PrintConditionColor applies to. When PrintConditionColor is present, the parent Attribute, Color / @MediaType , is ignored. If Media is not specified, PrintConditionColor applies to print Processes with a matching PrintConditionName. |
|
|
TransferCurve of the PrintConditionColor . If not specified, defaults to the parent Color / TransferCurve . |
Example 7-8: Color
This is an example of the structure for Color . The transfer curves in this example are defined for process CMYK and sRGB, independently.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< Color Class = "Parameter" ID = "C000" Status = "Available" CMYK = "0.2 0.3 0.4 0.5"
Density = "3.14" Lab = "20. 30. 40." MediaType = "Coated"
Name = "PANTONE Deep Blue" sRGB = "0.6 0.7 0.9" >
< TransferCurve Curve = "0 0 .5 .4 1 1" Separation = "Cyan" />
< TransferCurve Curve = "0 0 .5 .6 1 1" Separation = "Magenta" />
< TransferCurve Curve = "0 0 1 1" Separation = "Yellow" />
< TransferCurve Curve = "0 0 1 1" Separation = "Black" />
< TransferCurve Curve = "0 0 1 1" Separation = "sRed" />
< TransferCurve Curve = "0 0 1 1" Separation = "sGreen" />
< TransferCurve Curve = "0 0 1 1" Separation = "sBlue" />
Example 7-9: ColorantControl: Content-Ignorant MIS
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<!--Simple colorantcontrol from MIS: CMYK + 1 spot+ 1 black text
< ColorantControl Class = "Parameter" ID = "r000004" ProcessColorModel = "DeviceCMYK"
<!--Note that all Strings in ColorantParams etc. use Color/@Name,
< SeparationSpec Name = "Spot1" />
< SeparationSpec Name = "BlackText" />
Example 7-10: ColorantControl: Synchronized with Input
Example of initial (previous) ColorantControl after synchronizing with input. This example specifies the replacement color name with a new ActualColorName Attribute in the Color Element. This approach has the disadvantage of needing a new Attribute. However, it has the following advantages
- no ambiguity in case of multiple names ( ColorantAlias is used only as a pure aliasing mechanism)
- The name is localized in the ColorPool , which should be more central and not differ, e.g. between proofing and final imaging.
- it is “easier” to implement
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<!--ColorantControl after prepress has correctly set ActualColorName based
< ColorantControl Class = "Parameter" ID = "r000004" ProcessColorModel = "DeviceCMYK"
<!--Note that all Strings in ColorantParams etc. use Color/@Name,
< SeparationSpec Name = "Spot1" />
< SeparationSpec Name = "BlackText" />
< ColorPoolRef rRef = "r000005" />
< ColorPool Class = "Parameter" ID = "r000005" Status = "Available" >
<!--Color that maps the predefined separation Black
ActualColorName is the new attribute that replaces
ExposedMedia/@DescriptiveName as the "Main" PDL color
< Color ActualColorName = "Schwarz" CMYK = "0 0 0 1" Class = "Parameter"
< Color ActualColorName = "Gelb" CMYK = "0 0 1 0" Class = "Parameter"
<!--ActualColorName defaults to Name if not specified-->
< Color CMYK = "1 0 0 0" Class = "Parameter" Name = "Cyan" />
< Color Class = "Parameter" Name = "Magenta" />
< Color ActualColorName = "Acme Aqua" CMYK = "0.7 0.2 0.03 0.1"
Class = "Parameter" Name = "Spot1" />
< Color ActualColorName = "VersionsText" CMYK = "0 0 0 1" Class = "Parameter"
Example 7-11: ColorantControl: Synchronized with Input with Alias
Example of initial ColorantControl after synchronizing with input that contains an alias
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< ColorantControl Class = "Parameter" ID = "r000004" ProcessColorModel = "DeviceCMYK"
<!--ColorantControl after prepress has correctly set ActualColorName based
<!--Note that all Strings in ColorantParams etc. use Color/@Name,
< SeparationSpec Name = "Spot1" />
< SeparationSpec Name = "BlackText" />
< ColorPoolRef rRef = "r000005" />
<!--ColorantAlias that maps the additional representations
(noir, schwarz) to the predefined separation Black-->
< ColorantAlias Class = "Parameter" RawNames = "6E6F6972 73636877E4727A"
ReplacementColorantName = "Black" >
< SeparationSpec Name = "noir" />
< SeparationSpec Name = "schwarz" />
< ColorPool Class = "Parameter" ID = "r000005" Status = "Available" >
<!-- ColorPool is same as previous example -->
Example 7-12: ColorantControl: with ColorantAlias/ReplacementColorantName
Example of many-to one substitution with ColorantAlias /@ ReplacementColorantName
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< ColorantControl Class = "Parameter" ID = "r000004" ProcessColorModel = "DeviceCMYK"
<!--ColorantAlias that maps the predefined separation Black-->
< ColorantAlias ReplacementColorantName = "Black" >
< SeparationSpec Name = "Schwarz" />
< SeparationSpec Name = "schwarz" />
Example 7-13: ColorantControl: with Invalid ColorantAlias/ReplacementColorantName
Invalid example of many-to one substitution with ColorantAlias /@ ReplacementColorantName
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< ColorantControl Class = "Parameter" ID = "r000004" ProcessColorModel = "DeviceCMYK"
<!--ColorantAlias that maps the predefined separation Black-->
< ColorantAlias ReplacementColorantName = "Black" >
< SeparationSpec Name = "Schwarz" />
< ColorantAlias ReplacementColorantName = "Black" >
< SeparationSpec Name = "schwarz" />
<ColorantControlLink Usage="Input" rRef="r000004"/>
7.2.27 ColorantAlias
ColorantAlias is a Resource that specifies a replacement colorant name string to be used instead of one or more named colorant strings. For example, SeparationSpec /@ Name = "Pantone 135 C" , "PANTONE 135" and ReplacementColorantName = "PANTONE 135 C" maps string values: "Pantone 135 C" and "PANTONE 135" to the string value: "PANTONE 135 C" . Note that ColorantAlias was elevated from a Subelement of ColorantControl to a top level Resource in JDF 1.2.
ColorantControl , ElementColorParams
|
Whitespace-separated list of hexBinary values. Each token represents the original 8-bit byte stream of the color specified in SeparationSpec . Used to transport the original byte representation of a color name when moving JDF tickets between computers with different locales. Exactly one token MUST be specified for each SeparationSpec in this ColorantAlias . The order of tokens MUST be identical to the order of the related SeparationSpec . |
||
|
The value of the colorant name string to be substituted for the colorant name strings in the SeparationSpec Resource list. |
||
Example 7-14: ColorantAlias/@RawNames
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< ColorantAlias Class = "Parameter" ID = "r000004" RawNames = "4772FC6E 6772FC6E"
ReplacementColorantName = "Green" Status = "Available" >
<!-- ColorantAlias that maps the additional representation (grün, Grün)
to the predefined separation Green -->
< SeparationSpec Name = "Grün" />
< SeparationSpec Name = "grün" />
<ColorantAliasLink Usage="Input" rRef="r000004"/>
7.2.28 ColorantControl
ColorantControl is a Resource used to control the use of color when processing PDL pages. The Attributes and Elements of the ColorantControl Resource describe how color information embedded in PDL pages is to be translated into Device colorant information.
Colorants are referenced in ColorantControl by name only. Additional details about individual colorants can be found in the Color Element of the ColorPool Resource. The ColorantControl Resources control which Device colorants will be used as well as how document colors will be converted into Device color spaces and how conflicting color information are to be resolved. Separation control is specified by the Process being present. For example:
ColorantControl can be used as follows to define the specific colorants of a targeted output DeviceNSpace when the DeviceNSpace process colors are the only colorants used on the Job:
- ColorantControl / ColorPool /@ ColorantSetName matches ColorantControl / DeviceNSpace /@ Name , and
- a ColorantControl / ColorPool / Color Resource (with correct Name of colorant and other defining Attributes) exists for each colorant of the DeviceNSpace as given in:
- ColorantControl / DeviceNSpace / SeparationSpec /@ Name .
ColorantControl can be used as follows to define the specific colorants of a targeted output when both CMYK process colors and separate spot colorants are used for the final production printing, but a local printer equivalent of the spot color is used for proofing:
- ColorPool /@ ColorantSetName is and expanded name set including Color Resources for the CMYK process primaries and the ReplacementColorantName spot colorant, and
- Then for that spot color...
- ColorPool / Color /@ Name
- ColorPool / Color /@ MappingSelection Attribute Value = "UseLocalPrinterValues" , (used by a ColorSpaceConversion Process only in the proofing instance).
- For proof printing:
- ColorantControl /@ ColorantParams does not list that spot colorant.
- For production printing:
- ColorantControl /@ ColorantParams and ColorantControl /@ ColorantOrder both include that spot colorant.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
ColorCorrection , ColorSpaceConversion , ConventionalPrinting , DigitalPrinting , ImageSetting , Interpreting , PreviewGeneration , Separation , Stripping , Trapping
|
If "true" , forces all colorants to be output as individual separations, regardless of any values defined in ColorantControl , (i.e., all separations in a document are assumed to be valid and are output individually). A value of "false" specifies to respect the parameters specified in ColorantControl and elsewhere in the JDF. |
||
|
Specifies the model to be used for rendering the colorants defined in color spaces into process colorants. DeviceN - The specific DeviceN color space to operate on is defined in the DeviceNSpace Resource. If this value is specified then the DeviceNSpace and ColorPool refelements must also be present. None - No Colorants other than those specified in ColorantParams MUST be output. New in JDF 1.4 |
||
|
Identify one or more named colorants that are to be replaced with a specified named colorant. The identified colorant remappings in this ColorantAlias may be consolidated for processing from the information received in the LayoutElement / ElementColorParams / ColorantAlias Resources with the Job content. Multiple ColorantAlias Elements with identical values of ColorantAlias /@ ReplacementColorantName MUST NOT be specified in the same ColorantControl resource context. |
||
|
List of colors that MUST be converted to process colors. Defaults to all colors that are neither listed in ColorantParams nor implied by ProcessColorModel . Application can issue a warning for all PDL Colors that are not in ( ColorantParams + ColorantConvertProcess + implied by ProcessColorModel ) lists. |
||
|
The ordering of named colorants to be processed, for example in the RIP. All of the colorants named must either occur in the ColorantParams list or be implied by the ProcessColorModel. If present, then only the colorants specified by ColorantOrder must be output. Colorants listed in the ColorantParams list, or implied by the ProcessColorModel , but not listed in ColorantOrder , must not be output. They must still be processed for side effects in the colorants that are listed such as knockouts or trapping. If not present, then all colorants specified in ColorantParams and implied by ProcessColorModel are output. The explicit or implied value of ColorantOrder may be modified by an implied Partition of the ColorantControlLink . If one or more ColorantControlLink / Part /@ Separation are specified, ColorantOrder is reduced to the list. It is an error to specify values of ColorantControlLink / Part /@ Separation that are not explicitly stated or implied by ColorantOrder . |
||
|
A set of named colorants. This list defines all the colorants that are expected to be available on the Device where the Process will be executed. Named colors found in the PDL that are not listed in ColorantParams will be implemented through their ProcessColorModel equivalents. (See ElementColorParams and ColorSpaceConversion Process.) The colorants implied by the value of ProcessColorModel are assumed and must not be specified in this list. The spot colors defined in ColorIntent / ColorsUsed will in general be mapped to ColorantParams for each spot color to be used as part of any Product Intent to Process conversion. |
||
|
Pool of Color Elements that define the specifics of the colors implied by ProcessColorModel and named in ColorantControl . ColorantControl uses a subset of the total ColorPool . The subset that ColorantControl uses from ColorPool is the subset of ProcessColorModel colors (possibly all), and the subset of spot colors (possibly all) designated to be processed in this instance using specific separation colorants. ColorPool in total includes spot colors in the Job for which a JDF process color equivalent mapping is required. Those colors are used by ColorSpaceConversion when ColorPool / Color /@ MappingSelection = "UseProcessColorValues" . In that case, the process color equivalent for the spot color is taken from the available information in the Color Resource for that spot color. |
||
|
Each Subelement identifies a colorant that is to be replaced by another colorant. |
||
|
The ordering of named colorants (e.g., order of laying them down) to be output on the Device, such as press modules. Note that this must be synchronized with the Device output ICC profile. All of the named colorants must occur in ColorantOrder if it is present. If ColorantOrder is not present, then all of the named colorants must occur in the ColorantParams list, or be implied by the ProcessColorModel . If the DeviceColorantOrder Element is not specified, the order for laying down colorants defaults to ColorantOrder . |
||
|
Defines the colorants that make up a DeviceN color space. The DeviceNSpace Attribute is required when the ProcessColorModel value is DeviceN . |
7.2.28.1 Element: ColorantConvertProcess
|
The names of the colorants that define the respective lists. |
7.2.28.2 Element: ColorantOrder
|
The names of the colorants that define the respective lists. |
7.2.28.3 Element: ColorantParams
|
The names of the colorants that define the respective lists. |
7.2.28.4 Element: DeviceColorantOrder
|
The names of the colorants that define the respective lists. |
7.2.28.5 Element: ColorSpaceSubstitute
|
A reference to a color space description that replaces the color space defined by the colorants described by the SeparationSpec Element(s). |
||
|
A list of names that defines the colorants to be replaced. This could be a single name in the case of a Separation color space, or more than one name in the case of a DeviceN color space. |
The following table describes which separations are output for various values of ProcessColorModel , ColorantOrder , ColorantControlLink , ColorantParams and DeviceColorantOrder . Note that all separations that are neither specified in ColorantParams nor implied by ProcessColorModel are mapped to the colors implied by ProcessColorModel prior to any color selection defined by ColorantOrder .
|
Separations that are output |
|||||
|---|---|---|---|---|---|
|
(If DeviceColorantOrder is not present then lay down order will be Cyan first, Magenta last.) |
|||||
|
DeviceN (with example N = 2 colorants as identified in DeviceNSpace ) |
The reordering is accomplished using DeviceColorantOrder . |
7.2.29 ColorControlStrip
This Resource describes a color control strip. The type of the color control strip is given in the StripType Attribute. The lower left corner of the control strip box is used as the origin of the coordinate system used for the definition of the measuring fields. It can be calculated using the following formula:
x
= X element of the
Center
Attribute
y
= Y element of the
Center
Attribute
w
= X element of the
Size
Attribute
h
= Y element of the
Size
Attribute
j
= Value of the
Rotation
Attribute
|
Position of the center of the color control strip in the coordinates of the MarkObject that contains this mark. Modification note: starting with JDF 1.4, Center is optional. |
||
|
Rotation in degrees. Positive graduation figures indicate counter-clockwise rotation; negative figures indicate clockwise rotation. |
||
|
Type of color control strip. This Attribute MAY be used for specifying a predefined, company-specific color control strip. |
||
|
Details of a CIELAB measuring field that is part of this ColorControlStrip . |
||
|
Details of a density measuring field that is part of this ColorControlStrip . |
||
|
Ordered list of separations that comprise the ColorControlStrip . If neither CIELABMeasuringField nor DensityMeasuringField are specified, the geometry is implied by the value of StripType . |
7.2.30 ColorCorrectionParams
This Resource provides the information needed for an operator to correct colors on some PDL pages or content Elements such as image, graphics or formatted text.
The preferred color adjustment method allows for multi-dimensional adjustments through the use of either an ICC Abstract profile or an ICC DeviceLink profile. The adjustments are not universally colorimetrically calibrated. However, when either of the ICC profile adjustment methods are used, these standard ICC profile formats can be interpreted and applied using generally recognized ICC profile processing techniques. Use of the ICC Abstract profile adjustment will cause the adjustment to be applied in ICC Profile Connection Space, after each source profile is applied, in sequence before final target color conversion. Use of the ICC DeviceLink profile adjustment will cause the adjustment to be applied in final target Device space, after the final target color conversion.
In addition to color adjustment using an ICC profile, the AdjustXXX Attributes each provide a direct color adjustment applied to the interpretation of the PDL data at an implementation dependent point in the processing after each source profile is applied (if source-to-destination color conversion is needed). The L*a*b* values range from -100 to +100 to indicate the minimum and maximum of the range that the system supports. A "0" value means no adjustment. The color adjustment Attributes differ from the Tone Reproduction Curve (TRC) Attributes that can be applied later in the processing path in two key ways. First, the AdjustXXX use, even when included in the Job, will vary as a function of Job content. Second, the data values associated with the AdjustXXX Attributes are arbitrary, and their interpretation will be printer dependent. For details about these Attributes, see Appendix E, “Color Adjustment Attribute Description and Usage” .
Note: These color adjustments are not available in any Intent Resource , (e.g., ColorIntent ). In order to request such adjustment in a Product Intent Job ticket supplied to a print provider, attach to a Product Intent Node an incomplete ColorCorrection Process with a ColorCorrectionParams Resource specifying the requested AdjustXXX Attributes.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
|
Identifies the preferred ICC color-management system to use when performing color transformations. When specified, this Attribute overrides any default selection of a color management system by an application and overrides the “CMM Type” value (bytes 4-7 of an ICC Profile Header) in any of the Job related ICC profiles. This string Attribute Value identifies the manufacturer of the preferred CMM and must match one of the registered four-character ICC CMM Type values. Values include those from: ICC Manufacturer's Signature Registry at http://www.color.org . Example values: "ADBE" for the Adobe CMM and “ KODA ” for the Kodak CMM. |
||
|
FileSpec ( FinalTargetDevice ) ? |
A FileSpec Resource pointing to an ICC profile that describes the characterization of the final output target Device. |
|
|
FileSpec ( WorkingColorSpace ) ? |
A FileSpec Resource pointing to an ICC profile that describes the assumed characterization of CMYK , RGB and Gray color spaces. |
|
|
List of ColorCorrectionOp Subelements. ColorCorrectionOp SHOULD contain the complete set of parameters for a given color correction operation. Otherwise the results are implementation dependent. |
7.2.30.1 Element: ColorCorrectionOp
|
Identifies which class(es) of incoming graphical objects will be operated on. ImagePhotographic - Contone images. ImageScreenShot - Images largely comprised of rasterized vector art. LineArt - Vector objects other than text. |
||
|
Specifies the L*a*b* adjustment in the Cyan/Red axis in the range -100 (maximum Cyan cast for the system) to + 100 (maximum Red cast for the system) while maintaining lightness. (See explanation above.) |
||
|
Specifies the L*a*b* adjustment in the Magenta/Green axis in the range -100 (maximum Magenta cast for the system) to + 100 (maximum Green cast for the system) while maintaining lightness. (See explanation above.) |
||
|
Specifies the L*a*b* adjustment in the Yellow/Blue axis in the range -100 (maximum Yellow cast for the system) to + 100 (maximum Blue cast for the system) while maintaining lightness. (See explanation above.) |
||
|
Specifies the L*a*b* contrast adjustment in the range -100 (minimum contrast for the system, (i.e., a solid midtone gray color)) to + 100 (maximum contrast for the system, (i.e., either use full color (the maximum is restricted by the system ink limit) or no color for each of Cyan, Magenta, Yellow and Black)). Increasing the contrast value increases the variation between light and dark areas and decreasing the contrast value decreases the variation between light and dark areas. (See explanation above.) |
||
|
Specifies the change in the L*a*b* hue in the range -180 to +180 of all colors by the specified number of degrees of the color circle. (See explanation above.) |
||
|
Specifies the decrease or increase of the L*a*b* lightness in the range -100 (minimum lightness for the system, (i.e., black)) to + 100 (maximum lightness for the system, (i.e., white)). Increasing the lightness value causes the output to appear lighter and decreasing the lightness value causes the output to appear darker. (See explanation above.) |
||
|
Specifies the increase or decrease of the L*a*b* color saturation in the range -100 (minimum saturation for the system) to +100 (maximum saturation for the system). Increasing the saturation value causes the output to contain more vibrant colors and decreasing the saturation value causes the output to contain more pastel and gray colors. (See explanation above.) |
||
|
Tags associated with individual objects that this ColorCorrectionOp MUST be applied to. Each tag specified in ObjectTags is logically anded with the object type(s) specified by SourceObjects , enabling first qualification by object type (such as image), and then tags associated with those objects. The values of ObjectTags depends on the PDL that the color correction is applied to. |
||
|
FileSpec ( AbstractProfile ) ? |
A FileSpec Resource pointing to an abstract ICC profile that has been devised to apply a preference adjustment. (See explanation of adjustment at the beginning of this section.) |
|
|
FileSpec ( DeviceLinkProfile ) ? |
A FileSpec Resource pointing to an ICC profile that describes the characterization of an abstract profile for specifying a preference adjustment. (See explanation of adjustment at the beginning of this section.) |
7.2.31 ColorMeasurementConditions
This Resource contains information about the specific measurement conditions for spectral or densitometric color measurements. Spectral measurements refer to [CIE 15:2004] and [ISO13655:1996] . The default measurement conditions for spectral measurements are illuminant D50 and 2 degree observer.
Density measurements refer to [ISO5-3:1995] and [ISO5-4:1995] . The default measurement conditions for densitometric measurements are density standard ISO/ANSI Status T , calibration to absolute white and using no polarization filter.
CIELABMeasuringField , Color , DensityMeasuringField , Media , PrintCondition
7.2.32 ColorPool
The ColorPool Resource contains a pool of all Color Elements referred to in the Job. In general, it will be referenced as a ResourceRef from within Resources that require access to color information.
ColorIntent , NumberingIntent , ByteMap , ColorantControl , FormatConversionParams , LayoutElement , PageList
|
A string used to identify the named colorant parameter set. This string will be used to identify a set of color definitions (typically associated with a particular class of Job or a particular press). Note: This value will typically be identical to ColorIntent /@ ICCColorStandard or ColorIntent /@ ColorStandard . |
||
|
Color * |
7.2.33 ColorSpaceConversionOp
Note: ColorSpaceConversionOp was elevated from a Subelement of ColorSpaceConversionParams in JDF 1.2. The ColorSpaceConversionOp Resource identifies a type of object, defines the source color space for that type of object, and specifies the behavior of the conversion operation for that type of object. Many of these Attribute descriptions refer to ICC Color Profiles [ICC.1] . See also the International Color Consortium (ICC) Web site at http://www.color.org .
ColorSpaceConversionParams , ElementColorParams
|
If "true" , specifies that embedded source ICC profiles MUST be ignored as part of the selection criteria for this ColorSpaceConversionOp . If "true" , FileSpec ( PDLSourceProfile ) is ignored. |
||
|
Tags associated with individual objects that this ColorSpaceConversionOp MUST be applied to. Each tag specified in ObjectTags is logically anded with the object type(s) specified by SourceObjects , enabling first qualification by object type (such as image), and then tags associated with those objects. The values of ObjectTags depends on the PDL that the color space conversion is applied to. |
||
|
Controls which of five functions the color space conversion utility performs. Convert - Transforms graphical elements to final target color space. Tag - Associates appropriate working space profile with uncharacterized graphical element. Untag - Removes all profiles and color characterizations from graphical elements. Retag - Equivalent to a sequence of Untag -> Tag , where the Untag -> Tag sequence is only applied to those objects selected by this ColorSpaceConversionOp . ConvertIgnore - Equivalent to a sequence of Untag -> Convert . Constraint: Operation must be specified in the context of ColorSpaceConversionParams / ColorSpaceConversionOp and must not be specified in the context of ElementColorParams / ColorSpaceConversionOp . |
||
|
Controls how the tints of black ( K in CMYK) are to be handled. If PreserveBlack is "false" , these colors are processed through the standard ICC workflow. If PreserveBlack is "true" , these colors are to be converted into other shades of black. The algorithm is implementation-specific. |
||
|
Identifies the rendering intents associated with SourceObjects Elements. Values are (ICC-defined [ICC.1] rendering intent values) : ColorSpaceDependent - The rendering intent is dependent on the color space. The dependencies are implementation specific. Modified in JDF 1.3 |
||
|
This feature controls what happens to gray values ( R = G = B) when converting from RGB to CMYK or the incoming graphical objects indicated by SourceObjects . In the case of MS Office applications and screen dumps, there are a number of gray values in the images and line art. Printers do not want to have CMY under the K because it creates registration problems. They prefer to have K only, so the printer converts the gray values to K. Gray values that exceed the RGBGray2BlackThreshold are not converted. RGBGray2Black and RGBGray2BlackThreshold are used by the ColorSpaceConversion Process in determining how to allocate RGB values to the black ( K ) channel. After the ColorSpaceConversion Process is completed, the Rendering Process uses AutomatedOverPrintParams to determine overprint behavior for the previously determined black ( K ) channel. |
||
|
A value between "0.0" and "1.0" which specifies the threshold value above which the Device must not convert gray ( R = G = B) to black ( K only) when RGBGray2Black is "true" . So a "0" value means convert only R = G = B = 0 (black) to K only. A value of "1" specifies that all values of R = G = B are converted to K if RGBGray2Black = "true" . |
||
|
Identifies which of the incoming color spaces will be operated on. Values are from: Table 7-114, “SourceCS Attribute Values”. Note: see Table 7-115, “Mapping of SourceCS enumeration values to color spaces in the most common input file formats”. |
||
|
List of object Classes that identifies which incoming graphical objects will be operated on. ImagePhotographic - Contone images. ImageScreenShot - Images largely comprised of rasterized vector art. LineArt - Vector objects other than text. |
||
|
Identifies the rendering intent transform elements to be selected from the source profile that will be used to interpret objects of type identified by the SourceObjects and SourceCS Attributes. Default value is from: @ RenderingIntent . Values are (ICC-defined [ICC.1] rendering intent values) : ColorSpaceDependent - The rendering intent is dependent on the color space. The dependencies are implementation specific. Modified in JDF 1.3 Note: The SourceRenderingIntent will pertain to the source profile used in a particular ColorSpaceConversion Process, (e.g., sources can be the native original color space, an intermediate working color space or an reference output simulation color space). |
||
|
DeviceNSpace Resource that describe the DeviceN color space on which to operate when SourceCS = "DeviceN" . Individual colorant definitions for the colorant names given in DeviceNSpace are provided in the ColorantControl / ColorPool Resource, which must also be present |
||
|
FileSpec ( AbstractProfile ) ? |
A FileSpec Resource pointing to an ICC profile [ICC.1] that de-scribes the characterization of an Abstract Profile for specifying a preference adjustment. |
|
|
FileSpec ( DeviceLinkProfile ) * |
A FileSpec Resource pointing to a Device Link ICC profile [ICC.1] . The Source colorspace of the referenced Device Link Profile SHOULD match that of the profile identified by FileSpec ( PDLSourceProfile ) and the destination color space SHOULD match that of the destination profile identified by ColorSpaceConversionParams . Multiple Device Link ICC profiles should be provided where each profile specifies a different rendering intent. This is important in the case where multiple PDL content objects of the colorspace specify different rendering intents. FileSpec ( DeviceLinkProfile ) MUST be ignored when the Operation is "Tag" or "Retag" . Note: an ICC Device Link profile contains only one transform with one color rendering intent. Note: this Element was added to JDF 1.3 Errata. Modification note: starting with JDF 1.4, multiple FileSpec ( DeviceLinkProfile ) Elements are allowed. |
|
|
FileSpec ( PDLSourceProfile ) ? |
A FileSpec Resource describing an ICC profile that describes a profiled source space that this ColorSpaceConversionOp should operate on. When present, only objects that specify the SourceCS along with the specified profile are selected. Note: the FileSpec /@ Checksum or FileSpec /@ FileVersion Attributes SHOULD be used to positively identify the ICC profile when available (the specified attribute's value should match the ICC ProfileID field). |
|
|
FileSpec ( SourceProfile ) ? |
A FileSpec Resource pointing to an ICC profile [ICC.1] that describes the assumed source color space. If FileSpec ( SourceProfile ) is specified, it MUST be used as the profile for the source object's color space during a Convert , Tag , or Retag operation, as specified by @ Operation . FileSpec ( SourceProfile ) MUST be present for Tag or Retag operations, as specified by @ Operation . |
|
|
SeparationSpec Resource(s) defining on which separation(s) to operate when SourceCS = "Separation" . |
-- Attribute: SourceCS
|
Operates on all source colorspaces. This is useful when specifying a Convert operation using all PDL source-supplied characterizations with a JDF-supplied final target device profile. |
|
|
defines a calibrated Device independent representation of Gray. |
|
|
defines a calibrated based Device independent representation of RGB. Note: JDF 1.1 defined that CalRGB be treated as RGB , CalGray as Gray and ICCBased color spaces as one of Gray , RGB or CMYK depending on the number of channels. |
|
|
Operates on CIE-based color spaces ( CIEBasedA , CIEBasedABC , CIEBasedDEF and CIEBasedDEFG ). |
|
|
Operates on DeviceCMYK color spaces. If IgnoreEmbeddedICC is "true" , then PDL DeviceCMYK color spaces that have an ICC-based characterization (/DefaultCMYK in PDF having an ICC-based characterization) are treated as uncharacterized DeviceCMYK color spaces, and operated on by SourceCS = "CMYK" .. |
|
|
Identifies the source color encoding as a DeviceN color space. The specific DeviceN color space to operate on is defined in the DeviceNSpace Resource. If DeviceN is specified, then the DeviceNSpace and ColorantControl / ColorPool refelements must also be present. |
|
|
Operates on Device independent color spaces (equivalent to Calibrated , CIEBased , ICCBased , Lab or YUV ). |
|
|
Operates on DeviceGray . If IgnoreEmbeddedICC is "true" , then PDL DeviceGray color spaces that have an ICC-based characterization (/DefaultGray in PDF having an ICC-based characterization) are treated as uncharacterized DeviceGray color spaces, and operated on by SourceCS = "Gray" . |
|
|
Operates on color spaces defined using ICC profiles. The ICCBased value includes EPS, TIFF or PICT files with embedded ICC profiles. See [ICC.1] . If IgnoreEmbeddedICC is "true" then nominally ICCBased files or elements are to be treated as being encoded in the Alternate or underlying color space defined in the PDL, and a ColorSpaceConversionOp where SourceCS = "DevIndep" is not to be applied unless that color space is also Device independent. |
|
|
Operates on DeviceCMYK PDL data having an associated ICC-based characterization (/DefaultCMYK in PDF having an ICC-based characterization). |
|
|
Operates on DeviceGray PDL data having an associated ICC-based characterization (/DefaultGray in PDF having an ICC-based characterization). |
|
|
defines an ICC based Device independent representation of LAB |
|
|
Operates on DeviceRGB PDL data having an associated ICC-based characterization (/DefaultRGB in PDF having an ICC-based characterization). |
|
|
Operates on DeviceRGB . If IgnoreEmbeddedICC is "true" , then PDL DeviceRGB color spaces that have an ICC-based characterization (/DefaultRGB in PDF having an ICC-based characterization) are treated as uncharacterized DeviceRGB color spaces, and operated on by SourceCS = "RGB" . |
|
|
Operates on Separation color spaces (spot colors). The specific separation(s) to operate on are defined in the SeparationSpec Resource(s). If no SeparationSpec is defined, the operation will operate on all the separation color spaces in the input RunList . |
|
|
Operates on YUV (Also known as YCbCr). See [CCIR601-2] |
DevIndep has been retained for backwards compatibility with JDF 1.1 and because there will probably be cases where the same processing is to be applied to all Device independent spaces. An equivalent “ DevDep ” has not been added because it's less likely that all Device-dependent spaces are to be treated in the same way. The following table summarizes how the SourceCS Attribute is mapped to/from different file formats.
(1) When IgnoreEmbeddedICC = "false" , DeviceCMYK , DeviceRGB and DeviceGray in PDF files are to be mapped through DefaultCMYK, DefaultRGB or DefaultGray color spaces if present, before determining whether to apply this operation.
(2) Where a Pattern or Indexed color space has been used, the base color space is used to determine whether to apply this operation.
7.2.34 ColorSpaceConversionParams
This set of parameters defines the rules for a ColorSpaceConversion Process, the Elements of which define the set of operations to be performed. Information inside the ColorSpaceConversionOp Elements, described below, defines the operation and identifies the color spaces and types of objects to operate on. Other Attributes define the color management system to use, as well as the working color space and the final target Device.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
|
Identifies the preferred ICC color management system to use when performing color transformations. When specified, this Attribute overrides any default selection of a color management system by an application and overrides the “CMM Type” value (bytes 4-7 of an ICC Profile Header) in any of the Job related ICC profiles. This string Attribute Value identifies the manufacturer of the preferred CMM and must match one of the registered four-character ICC CMM Type values. Values include those from: ICC Manufacturer's Signature Registry at http://www.color.org . Example values: " ADBE " for the Adobe CMM and " KODA " for the Kodak CMM. |
||
|
When "true" , incoming Device-independent colors are processed to the selected Device space. If the chosen operation is Untag and the characterization data are in the form of an ICC profile, then the profile is removed. Otherwise, these colors are left untouched. The functionality of ConvertDevIndepColors is superseded by including one or more ColorSpaceConversionOp with SourceCS = "DevIndep" in JDF 1.1. |
||
|
This Attribute specifies where to obtain the destination profile for the current iteration of the ColorSpaceConversion Process, (i.e., either from the PDL (PDF/X output intent dictionary) or supplied in the JDF ColorSpaceConversionParams Resource). ICCProfileUsage provides an order precedence.
|
||
|
FileSpec ( FinalTargetDevice ) ? |
A FileSpec Resource pointing to an ICC profile that describes the characterization of the final output target Device. |
|
|
FileSpec ( WorkingColorSpace ) ? |
A FileSpec Resource pointing to an ICC profile that describes the assumed characterization of CMYK , RGB and Gray color spaces. |
|
|
List of ColorSpaceConversionOp Elements, each of which identifies a type of object, defines the source color space for that type of object, and specifies the behavior of the conversion operation for that type of object. The XML order of ColorSpaceConversionOp Elements is significant, and when multiple elements apply to the same object, they are applied in that XML order. If multiple, overlapping ColorSpaceConversionOp Elements are specified, the operations that define individual SourceCS override the Elements specifying groups of source color spaces. ColorSpaceConversionOp SHOULD contain the complete set of parameters for a given color space conversion operation. Otherwise the results are implementation dependent. |
7.2.35 ComChannel
A communication channel to a person or company such as an email address, phone number or fax number.
Contact , CustomerInfo / CustomerMessage , Person
|
Type of the communication channel. PrivateDirectory - Account of a registered customer of a certain service. (The list of the registered accounts is maintained by the service vendor). The ChannelTypeDetails Attribute has the name of the private directory service vendor. InstantMessaging - IM service address. The ChannelTypeDetails Attribute has the name of the IM service vendor |
||
|
Description of the value of the ChannelType Attribute. Consumer treats this value as the service vendor name if ChannelType is "PrivateDirectory" or "InstantMessaging" . Values include those from: Table 7-118, “ChannelTypeDetails Attribute - predefined values for certain ChannelType values”. |
||
|
Business - Business purpose usage, (e.g., office phone number, fax). Private - Private purpose usage, (e.g., private phone number, fax, Email). DayTime - Office hours in the time zone of the recipient. NightTime - Out-of-office hours in the time zone of the recipient. WeekEnd - Out-of-office hours in the time zone of the recipient. |
||
|
Locator of this type of channel in a form, such as a phone number, a URL or an Email address. If a URL is defined for the ChannelType , it is recommended to use the URL syntax specified in [RFC2368] for “ mailto ” URLs, [RFC3966] for “tel” URLs and [RFC3986] for URLs in general, as follows: "mailto:a@b.com" - instead of "a@b.com" if ChannelType = "Email" , |
Example 7-15: ComChannel for Telephone
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< ComChannel Class = "Parameter" ID = "cc000004" ChannelType = "Phone"
ChannelTypeDetails = "Mobile" ChannelUsage = "Business"
Locator = "tel:+44-07808-907-919" Status = "Available" />
Example 7-16: ComChannel for Instant Messaging
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< ComChannel Class = "Parameter" ID = "cc000004" ChannelType = "InstantMessaging"
ChannelTypeDetails = "MyIMService" ChannelUsage = "Private"
Locator = "123456789" Status = "Available" />
<ComChannelLink Usage="Input" rRef="cc000004"/>
7.2.36 Company
Specifies contacts to a company including detailed information about contact persons and addresses. Use @ ProductID when a unique identifier for the Company is required. This structure can be used in many situations where addresses or contact persons are needed. Examples of contacts are customer, supplier, company and addressees. The structure is derived from the vCard format. It comprises the organization name and organizational units (ORG) of the organizational properties defined in the vCard format. The corresponding XML types of the vCard are quoted in the table.
7.2.37 Component
Component is used to describe the various versions of semi-finished goods in the press and postpress area, such as a pile of folded Sheets that have been collected and are then be joined and trimmed. Nearly every postpress Process has a Component Resource as an input as well as an output. Typically the first components in the Process chain are some printed Sheets or ribbons, while the last component is a book or a brochure.
The descriptions of Component -specific Attributes use some terms whose meaning depends on the culture in which they are used. For example, different cultures mean different things when they refer to the “front” side of a magazine. Other terms (e.g., binding) are defined by the production process and, therefore, do not depend on the culture.
Whenever possible, this specification endeavors to use culturally independent terms. In cases where this is not possible, Western style (left-to-right writing) is assumed. Please note that these terms might have a different meaning in other cultures, (i.e., those writing from right to left).
|
The table below describes the terms used to define the components.
Bundle / BundleItem , DigitalPrintingParams , FeedingParams / Feeder , FeedingParams / CollatingItem
Condition, RibbonName , SheetName , SignatureName , WebName
Any Product Intent Node (Section 6.3, “Product Intent Descriptions”), ConventionalPrinting , DigitalPrinting , Varnishing , BlockPreparation , BoxFolding , BoxPacking , Bundling , CaseMaking , CasingIn , ChannelBinding , CoilBinding , Collecting , CoverApplication , Creasing , Cutting , Embossing , EndSheetGluing , Feeding , Folding , Gathering , Gluing , HeadBandApplication , HoleMaking , Inserting , Jacketing , Labeling , Laminating , Numbering , Palletizing , Perforating , PlasticCombBinding , PrintRolling , RingBinding , ShapeCutting , Shrinking , SpinePreparation , SpineTaping , Stacking , StaticBlocking , Stitching , Strapping , StripBinding , ThreadSealing , ThreadSewing , Trimming , WebInlineFinishing , WireCombBinding , Wrapping
, Any Product Intent Node (Section 6.3, “Product Intent Descriptions”), ConventionalPrinting , DigitalPrinting , Varnishing , BlockPreparation , BoxFolding , BoxPacking , Bundling , CaseMaking , CasingIn , ChannelBinding , CoilBinding , Collecting , CoverApplication , Creasing , Cutting , Embossing , EndSheetGluing , Feeding , Folding , Gathering , Gluing , HeadBandApplication , HoleMaking , Inserting , Jacketing , Labeling , Laminating , Numbering , Palletizing , Perforating , PlasticCombBinding , PrintRolling , RingBinding , ShapeCutting , Shrinking , SpinePreparation , SpineTaping , Stacking , StaticBlocking , Stitching , Strapping , StripBinding , ThreadSealing , ThreadSewing , Trimming , WebInlineFinishing , WireCombBinding , Wrapping
|
AssemblyIDs of the Assembly , AssemblySection or StrippingParams ( BinderySignatureName ) which this Component carries. |
||
|
Size ( F1,F2 ) (See Figure 7-14, “Box packing” ) of the two top flaps of a carton for shipping. must not be specified unless ProductType = "Carton" . |
||
|
Specifies the category of the component. Block - Folded or stacked product, (e.g., book block). Other - The Component describes a sample that has not been produced in this Job. Examples are perfume samples, CDs or toys that are inserted into a printed product. New in JDF 1.3 Ribbon - The Component is a ribbon on a Web Press. Sheet - Single layer (Sheet) of paper. Web - The Component is a Web on a Web Press. FinalProduct - The Component is the final product that was ordered by the customer. PartialProduct - The Component is an intermediate product that will be input to a following Process. Proof - The Component is a proof., e.g., a press proof or output from a digital press. Note that in JDF 1.2, proof was defined in the 1st list of categories, above. Modified in JDF 1.3 Constraint: further details of the component are specified in ProductType . At most one of "FinalProduct" , "PartialProduct" or "Proof" must be specified in addition to one of the first five enumerations specified as values. |
||
|
The dimensions of the component. These dimensions may differ from the original size of the original product. For example, the dimensions of a folded Sheet may be unequal to the dimensions of the Sheet before it was folded. The dimension is always the bounding box around the Component . If not specified, a portrait orientation (Y > X) is assumed Note: It is crucial for enabling postpress to specify Dimensions unless they really are unknown. |
||
|
If "true" , the Component is waste from a previous Process that can be used to set up a Machine. Deprecation note: starting with JDF 1.4, use Partitioning with Condition instead of IsWaste . |
||
|
Maximum temperature the Component can resist (in degrees centigrade). The default setting is to impose no restriction in terms of heat, (e.g., fusers in electrophotographic Process or shrink wrapping). |
||
|
Expansion of the overfold of a Component . This Attribute is needed for the Inserting or other postpress Processes. |
||
|
List of the indices of the PageData Elements of the PageList specified in this Component . |
||
|
Type of product that this component specifies. Values include those from : Table 7-122, “ProductType Attribute Values”. |
||
|
Additional details of the product: If ProductType = "BlankBox" or ProductType = "FlatBox" , ProductTypeDetails specifies a box type: e.g. [ECMA] , [FEFCO] or company internal box type standard. NewspaperNormal - Standard newspaper. NewspaperMixed - multiple Component Resources of a newspaper are produced in parallel. NewspaperCombi - Component Resources are collected to one Component in an inline production chain after press. |
||
|
Total amount of individual Reader Pages that this Component contains. Count of -1 means “unknown.” If not specified, the value is unknown. |
||
|
Only used if contains (@ ComponentType , "Block" ) and Layout is present. Position of the block on the Layout in SurfaceContentsBox coordinates used in this Component . |
||
|
must not be specified unless contains (@ ComponentType , "Ribbon" ). RibbonName of the ribbon used in this Component . Deprecation note: starting with JDF 1.3, use a direct reference to the Layout Partition that represents the ribbon. |
||
|
must not be specified unless contains (@ ComponentType , "Sheet" ) or contains (@ ComponentType , "Block" ). Matches the Layout / Signature / Sheet /@ Name used in this Component . Deprecation note: starting with JDF 1.3, use a direct reference to the Layout Partition that represents the Sheet. |
||
|
must not be specified unless contains (@ ComponentType , "Ribbon" ). WebName of the ribbon used in this Component . Deprecation note: starting with JDF 1.3, use a direct reference to the Layout Partition that represents the Web. |
||
|
Total amount of individual surfaces that this Component contains. Note: a sheet always has 2 Surfaces regardless of the number of images or reader pages. In case of homogeneous Component Elements, SurfaceCount refers to surfaces with a size of Component /@ Dimensions |
||
|
Matrix describing the transformation of the orientation of a Component for the Process using this Resource as input. This is needed to convert the coordinate system of the Component to the coordinate system of the Process. When this Attribute is not present, the identity matrix (1 0 0 1 0 0) is assumed. In version 1.1 and beyond, use ResourceLink /@ Transformation or ResourceLink /@ Orientation . |
||
|
Assembly ? |
Specifies the assembly of the Component . In case of a newspaper-Web Press, the output Component may already be built up of several “booklets”. AssemblyIDs additionally specifies which AssemblySection Elements of the Assembly belong to this Component . |
|
|
Bundle ? |
Description of a Bundle of Component Resources if the Component represents multiple individual items. If no Bundle is present, the Component represents an individual item. Note that it is essential to keep a reference of the child Component Resources that comprise a Component , as this information is useful to postpress Processes. |
|
|
A stack of components can be processed using physical separators. This is useful in operations such as feeding. |
||
|
Sheet ? |
The Sheet Resource that describes the details of this Component if it contains (@ ComponentType , "Sheet" ) or contains (@ ComponentType , "Block" ). Replaced with Layout in JDF 1.2 and beyond. The Sheet in the referenced Layout is accessed by matching SourceSheet with Layout / Signature / Sheet /@ Name |
|
|
Layout ? |
Specifies the original Layout of the source Sheet of the Component if it contains (@ ComponentType , "Sheet" ) or contains (@ ComponentType , "Block" ). The original Sheet is the Layout Partition Element where SourceSheet matches the Layout /@ SheetName used in this Component |
|
|
Media ? |
Media for the component. The coordinate system of Media coincides with the coordinate system of the component. |
|
|
PageList ? |
Specification of page metadata for pages described by this Component . |
Example 7-17: Component: Partitioned by the Condition Partition Key
The Condition Partition Key describes whether a Component Partition is waste and what type of waste it is. The amount of each Condition , in the standard manner for Partitioned Resources. See Section 3.10.5, “Description of Partitioned Resources”.)
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID = "IS123" Status = "Waiting"
Type = "Product" JobPartID = "ID20" Version = "1.4" >
< Component Class = "Quantity" ID = "Res6" PartIDKeys = "Condition" Status = "Available"
< Component Condition = "Good" IsWaste = "false" />
< Component Condition = "Waste" IsWaste = "true" />
< ComponentLink Usage = "Output" rRef = "Res6" >
< PartAmount Amount = "2970" >
7.2.38 Contact
Element describing a contact to a person or address.
Abstract Physical Resource , ArtDeliveryIntent , ArtDeliveryIntent / ArtDelivery , DeliveryIntent , DeliveryIntent / DropIntent , ApprovalParams / ApprovalPerson , ApprovalSuccess / ApprovalDetails , ContentList / ContentData / ContentMetadata , CustomerInfo , DeliveryParams , DeliveryParams / Drop , DigitalDeliveryParams , OrderingParams
|
Classification of the contact. Accounting - Address of where to send to the bill. Administrator - Person to contact for queries concerning the execution of the Job. Agency - The contact is an employee of an Agency. New in JDF 1.4 Approver - Person who approves this Job. New in JDF 1.2 ArtReturn - Return delivery or pickup address for artwork of this Job. Billing - Contact information that refers to a payment method, (e.g., credit card). Delivery - The delivery address for all products of this Job. DeliveryCharge - The Contact is charged for delivery of this Job. Owner - The owner of a Resource. Pickup - The pickup address for all products of this Job. Sender - The source address of the delivery. New in JDF 1.2 Supplier - Address of a supplier of needed goods. SurplusReturn - Return delivery or pickup address for surplus products of this Job. |
||
|
Details of the Contact's role or roles. For instance, if contains (@ ContactTypes, "Delivery" ) this could be a description for which delivery location this Contact is responsible. |
||
|
Address ? |
||
|
Communication channels to the contact. These Elements define communication channels that may be assigned to multiple Persons, for instance the communication channel of a reception area. |
||
|
Company ? |
Company that this Contact is associated with. |
|
|
Person ? |
7.2.39 ContactCopyParams
Element describing the parameters of ContactCopying .
7.2.40 ContentList
ContentList provides a list of ContentData Elements.
PublishingIntent , LayoutElement , PageList
|
Details of the individual content element. A ContentData Element is referred to by its ID, i.e. the value of ContentData /@ ID . Modification note: before JDF 1.4, a ContentData Element was referred to by its index in ContentList with the warning that ContentData elements not be removed or inserted in a position other than the end of the list. |
7.2.40.1 Element: ContentData
ContentData defines the additional metadata of individual elements of a page. If the ContentList is Partitioned, the index refers to ContentData Elements in the respective leaves of the Partitioned ContentList . The index restarts at 0 with each Partitioned leaf.
|
Identification of the Resource, (e.g., in a catalog environment). |
||
|
List of ContentData / ID values that specify the ContentData Elements children of this ContentData Element. For instance, a book may refer to individual chapters. The reference ContentData object MUST reside in the same ContentList as this ContentData . |
||
|
Values include those from: Table 7-127, “ContentType Attribute Values”. |
||
|
If "true" , the ContentData has no content marks and is blank. |
||
|
ID of the Job that this ContentData belongs to. |
||
|
An ID of the ContentData as defined in the MIS system. |
||
|
Container for document related metadata such as ISBN, Author etc. |
||
|
Color details of the ContentData Element. |
||
-- Attribute: ContentType
7.2.40.2 Element: ContentMetadata
ContentMetadata is a container for metadata pertaining to this ContentData Element. Additional metadata fields may be created using GeneralID .
|
Comment ? |
If required, an abstract should be specified in Comment [@ Name = "Abstract" ]. |
|
|
Contact * |
||
|
Employee * |
If required, the author should be specified in an Employee [contains(@ Roles , "Author" )]. |
|
|
Part ? |
If present, conserves the values of the specified Partition Keys related to the content being processed. It is illegal to set Partition Key values where that key is used to explicitly Partition the referencing Resource, or is implied by that Resource. Note: this allows Partition Keys and values to be conserved in a RunList ( Surfaces ) or Component . |
Example 7-18: ContentList
<? xml version = "1.0" encoding = "UTF-8" ?>
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1"
ID = "n071030_02242300_000002" JobPartID = "n071030_02242300_000002"
Status = "Waiting" Type = "Approval" Version = "1.4"
xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
<!--Generated by the CIP4 Java open source JDF Library version : CIP4 JDF
< Created AgentName = "CIP4 JDF Writer Java" AgentVersion = "1.3 BLD 47"
Author = "CIP4 JDF Writer Java 1.3 BLD 47"
ID = "a071030_02242331_000003" TimeStamp = "2007-10-30T14:24:23+01:00" />
< ApprovalParams Class = "Parameter" ID = "ID345" Status = "Available" />
< ApprovalSuccess Class = "Parameter" ID = "ID346" Status = "Unavailable" />
< RunList Class = "Parameter" ID = "r071030_02242378_000004"
< PageListRef rRef = "PageList" />
< PageList Class = "Parameter" ID = "PageList" Status = "Available" >
< ContentListRef rRef = "ContentList" />
< ContentList Class = "Parameter" ID = "ContentList" Status = "Available" >
< ContentData ContentListIndex = "1 2 3" >
< ContentMetadata ISBN = "0123456789" Title = "book thing" >
< Comment ID = "c071030_022423109_000005" Name = "Abstract" >
Abstract of the book in english
< Contact Class = "Implementation" ContactTypes = "Editor" >
< Person Class = "Parameter" DescriptiveName = "authorName"
< ContentMetadata Title = "Chapter 1" >
< Contact Class = "Implementation" ContactTypes = "Customer" >
< Person Class = "Parameter" DescriptiveName = "authorName1"
< ContentMetadata Title = "Chapter 2 " >
< Contact Class = "Implementation" ContactTypes = "Customer" >
< Person Class = "Parameter" DescriptiveName = "authorName2"
< ContentMetadata Title = "Chapter 3" >
< Contact Class = "Implementation" ContactTypes = "Customer" >
< Person Class = "Parameter" DescriptiveName = "authorName3"
< RunListLink Usage = "Input" rRef = "r071030_02242378_000004" />
< ApprovalParamsLink Usage = "Input" rRef = "ID345" />
Example 7-19: ContentList: Extended with ISBN, Author, etc.
Example of ContentList with ISBN, Author, etc.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<!-- Information about the input (file, author) -->
< RunList ID = "NodeIDRunList" Status = "Available" Class = "Parameter" >
< LayoutElementRef rRef = "NodeIDLE" />
< new:DocumentInfo Title = "This is the title of the book"
ISBN = "0123456789" xmlns:new = "new schema URI" >
<!-- Multi-lines string for Abstract -->
This is the abstract of the book
<!-- List of authors. Using a PersonRef allows reusing the same
< new:Author Subject = "Preface" >
< PersonRef rRef = "AuthorID1" />
< new:Author Subject = "Content" >
< new:PersonRef rRef = "AuthorID2" />
< new:PersonRef rRef = "AuthorID3" />
< LayoutElement ID = "NodeIDLE" Status = "Available" Class = "Parameter" >
< FileSpec URL = "file:////hotfolder/files/Document2747.pdf"
MimeType = "application/pdf" UserFileName = "JDF1.3.pdf" />
<!-- Information about the authors -->
< Person ID = "AuthorID1" Class = "Parameter" Status = "Available" FirstName = "James"
FamilyName = "Smith" JobTitle = "Author" />
< Person ID = "AuthorID2" Class = "Parameter" Status = "Available" FirstName = "John"
FamilyName = "Smith" JobTitle = "Author" />
< Person ID = "AuthorID3" Class = "Parameter" Status = "Available" FirstName = "William"
FamilyName = "Smith" JobTitle = "Author" />
<!-- Media: A3 white paper coated on both sides, 70 gr/m2 -->
< Media ID = "MediaID" Class = "Consumable" Status = "Available" Weight = "70"
Dimension = "1190 842" MediaType = "Paper" MediaColorName = "White"
FrontCoatings = "Coated" BackCoatings = "Coated" />
<!-- Media: A4 yellow paper for Banner Page -->
< Media ID = "MediaID2" Class = "Consumable" Status = "Available" Weight = "70"
Dimension = "595 842" MediaType = "Paper" MediaColorName = "Yellow" />
<!-- Booklet layout + banner page with ISBN and Authors printed on it -->
< LayoutPreparationParams ID = "NodeIDLPP" Class = "Parameter" Status = "Available"
Sides = "TwoSidedFlipY" NumberUp = "2 1" BindingEdge = "Left"
PresentationDirection = "FoldCatalog" FoldCatalog = "F4-1"
FinishingOrder = "GatherFold" PageDistributionScheme = "Saddle" >
< InsertSheet SheetType = "JobSheet" SheetUsage = "Header" IsWaste = "true"
< MediaRef rRef = "MediaID2" />
< MarkObject CTM = "1 0 0 1 0 0" >
< JobField ShowList = "new:ISBN new:Authors" />
<LayoutPreparationParamsLink Usage="Input" rRef="NodeIDLPP"/>
<RunListLink Usage="Input" rRef="NodeIDRunList"/>
<MediaLink Usage="Input" rRef="MediaID"/>
7.2.41 ConventionalPrintingParams
This Resource defines the Attributes and Elements of the ConventionalPrinting Process. The specific parameters of individual printer modules are modeled by using the standard Partitioning methods. These methods are described in Section 3.10.5, “Description of Partitioned Resources”.
BlockName , FountainNumber , PartVersion , ProductionRun , RibbonName , Separation , SheetName , Side , SignatureName , WebName , WebProduct
|
If "true" , the proof is directly produced and subsequently an approval might be given by a person (e.g., the customer, foreman or floor manager) shortly after the first final-quality printed Sheet is printed. The approval is needed for the actual print run, and not for setup. If the ConventionalPrinting Process is waiting for a DirectProof , the Status of the JDF Node is switched to Stopped with the StatusDetails = "WaitForApproval" . |
||
|
The way in which ink is dried after a print run. |
||
|
Printing order of the surfaces on the Sheet. Either - Deprecated in JDF 1.2 Omit FirstSurface to specify either. |
||
|
State of the fountain solution module in the printing units. |
||
|
Identifies the location of the Media . The value identifies a physical location on the press, (e.g., unwinder 1, unwinder 2 and unwinder 3). If the media Resource is Partitioned by Location (see also Section 3.10.6.4, “Locations of Physical Resources”) there should be a match between one Location Partition Key and this MediaLocation value. Values include those from: Table C-21, “Input Tray and Output Bin Names” . |
||
|
Zero-based list of print modules that are available for printing. In some cases modules are not available because the print module is replaced with in-line tooling, (e.g., a perforating unit). If not specified, all modules are used for printing. The list is based on all modules of the printer and is not influenced by the value of ModuleIndex . Deprecation note: starting with JDF 1.4, the skipping of press modules is now handled by specifying ColorantControl / DeviceColorantOrder / SeparationSpec with no @ Name |
||
|
The way in which ink is dried in individual modules. |
||
|
Zero-based, ordered list of print modules that are to be used. ModuleIndex does not influence the ink sequence. It is used only to skip individual modules. The list is based on all modules of the printer and is not influenced by the value of ModuleAvailableIndex . Deprecation note: starting with JDF 1.4, the skipping of press modules is now handled by specifying ColorantControl / DeviceColorantOrder / SeparationSpec with no @ Name |
||
|
The width in points of the bottom margin measured inward from the edge of the Media with respect to the idealized Process coordinate system of the ConventionalPrinting Process. The Media origin is unaffected by NonPrintableMarginBottom . |
||
|
Same as NonPrintableMarginBottom except for the left margin. |
||
|
Same as NonPrintableMarginBottom except for the right margin. |
||
|
Index of the perfecting module if WorkStyle = "Perfecting" and multiple perfecting modules are installed. |
||
|
ContinuousFed - connected Sheets including fan fold. New in JDF 1.2 SheetFed - Separate cut Sheets. WebFed - Paper supplied to press on rolls. Deprecated in JDF 1.3 WebMultiple - Web Printing with multiple plates per cylinder. Generally used with Newspaper Web Printing. New in JDF 1.3 WebSingle - Web Printing with only one plate per cylinder. Generally used in commercial and publication workflows. New in JDF 1.3 |
||
|
Lay of input media. Reference edge of where paper is placed in a feeder. |
||
|
Maximum print speed in Sheets/hour (Sheet fed) or revolutions/hour (Web-Fed). Defaults to Device specific full speed. |
||
|
Details of the direct Approval Process, when DirectProof = "true" . |
||
|
Ink * |
Details of varnishing. Defines the varnish to be used for coatings on printed sides. Coatings are applied after printing all the colors. Other coating sequences must use the Partition mechanism of this Parameter Resource . Selective varnishing in print modules has to use a separate separation for the respective varnish. Varnish is specified by Ink / @Family = "Varnish" . If both Ink and ExposedMedia ( Plate ) are specified for a given separation, spot varnishing is specified. If only Ink and not ExposedMedia ( Plate ) is specified, overall varnishing is specified. In JDF 1.2 and beyond, Ink may occur in multiples in order to specify multiple layers of varnish. Note: The color inks are direct Input Resources of the Process and must not be specified here. Deprecation note: starting with JDF 1.4, use Varnishing . |
7.2.42 CostCenter
This Resource describes an individual area of a company that has separated accounting.
Notification , ResourceInfo , JobPhase , Device , Employee
7.2.43 CoverApplicationParams
CoverApplicationParams define the parameters for applying a cover to a book block.
|
Position of the cover in relation to the book block given in the cover-Sheet coordinate system. In JDF 1.2 and beyond, CoverOffset is implied by the transformation matrix of the ResourceLink / @Transformation of the cover’s ComponentLink . |
||
|
Score * |
7.2.44 CreasingParams
CreasingParams define the parameters for creasing or grooving a Sheet.
BlockName , RibbonName , SheetName , SignatureName , WebName
|
Crease * |
Defines one or more Crease lines. |
7.2.44.1 Element: Crease
Crease defines an individual crease line on a Component .
|
Relative distance of the reference edge relative to From in the coordinates of the incoming Component . The RelativeTravel is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0, which specifies the full length of the input component. |
||
|
Relative starting position of the tool. The RelativeStartPosition is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0 for each component of the XYPair, which specifies the full size of the input Component . |
||
|
Relative working path of the tool beginning at RelativeStartPosition . Since the tools can only work parallel to the edges, one coordinate must be zero. The RelativeWorkingPath is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0 for each component of the XYPair, which specifies the full size of the input Component . |
||
|
Starting position of the tool. If both StartPosition and RelativeStartPosition are specified, RelativeStartPosition is ignored. At least one of StartPosition or RelativeStartPosition must be specified. |
||
|
Distance of the reference edge relative to From . If both Travel and RelativeTravel are specified, RelativeTravel is ignored. At least one of Travel or RelativeTravel must be specified. |
||
|
Working path of the tool beginning at StartPosition . Since the tools can only work parallel to the edges, one coordinate must be zero. If both WorkingPath and RelativeWorkingPath are specified, RelativeWorkingPath is ignored. At least one of WorkingPath or RelativeWorkingPath must be specified. |
||
7.2.45 CustomerInfo
The CustomerInfo Resource contains information about the customer who orders the Job. CustomerInfo has been moved from a direct element of JDF to a Resource in JDF 1.3.
Before JDF 1.3, CustomerInfo was a Subelement of a JDF Node, and “inherited” down to child Nodes. Starting with JDF 1.3, CustomerInfo became a Resource that must be linked like any other Resource; there is no “inheritance”. Any Node MAY link to the same CustomerInfo Resource as its parent. A normative CustomerInfo is specified by a linked Resource. An informative CustomerInfo MAY be retrieved by searching for CustomerInfo of parent Nodes or Ancestor Elements
|
Customer identification used by the application that created the Job. This is usually the internal customer number of the MIS system that created the Job. |
||
|
The internal order number in the system of the customer. This number is usually provided when the order is placed and then referenced on the order confirmation or the bill. |
||
|
The internal project id in the system of the customer. This number might be provided when the order is placed and then referenced on the order confirmation or the bill. |
||
|
Array of ID s of any Elements that are specified as ResourceRef Elements. In version 1.1 it was the IDREF of a ContactRef . In JDF 1.2 and beyond, it is up to the implementation to maintain references. |
||
|
Company ? |
Resource Element describing the business or organization of the contact. In JDF 1.1 and beyond, Company affiliation of Contact Elements is specified in Contact . |
|
|
Contact * |
Resource Element describing contacts associated with the customer. There should be one Contact [contains (@ ContactTypes , "Customer" )]. Such a Contact specifies the primary customer’s name, address etc. |
|
7.2.45.1 Element: CustomerMessage
CustomerMessage is an abstract definition of messages to the customer. Formatting and details of the content generation of the message are system dependent.
|
Communication channel for the desired CustomerMessage . In case it is not specified, the CustomerMessage will be provided according to system predefined information. If multiple ComChannel Elements are specified, the CustomerMessage should be sent to all specified communication channels. |
||
|
Language to be used for the CustomerMessage . |
||
|
Defines the set of events that trigger a message that is defined or specified by the system. Values include those from: Table C-20, “MessageEvents and MilestoneType Values” . |
||
|
List of parameters to display in the CustomerMessage . Values include those from: Table I-1, “Predefined variables used in @XXXTemplate and @ShowList”. New in JDF 1.4 Modification note: starting with JDF 1.4, the values come from a common list rather than a list that is custom to this Element. |
7.2.46 CutBlock
Defines a cut block on a Sheet. It is possible to define a block that contains a matrix of elements of equal size. In this scenario, the intermediate cut dimension is calculated from the information about element size, block size and the number of elements in both directions. Each cut block has its own coordinate system, which is defined by the BlockTrf Attribute.
|
The AssemblyIDs of the Assembly , AssemblySection or StrippingParams [@ BinderySignatureName ] which are contained in this CutBlock . |
||
|
Element dimension in X and Y direction. The default value is equivalent to the XYPair value in BlockSize . |
||
|
Name of the block. Used for reference by the CutMark Resource. Note that CutBlock Resources are not Partitioned although they are nested. The semantics of nested CutBlock Elements are different. |
||
|
Block transformation matrix. Defines the position and orientation of the block relative to the Component coordinate system. |
||
|
SaveBlock - Protected block, cut only via outer contour. TempBlock - Auxiliary block that is not taken into account during cutting. |
||
|
Assembly ? |
Assembly that is referred to by AssemblyIDs or contains the AssemblySection that is referred to by AssemblyIDs. |
7.2.47 CutMark
This Resource, along with CutBlock , provides the means to position cut marks on the Sheet. After printing, these marks can be used to adapt the theoretical block positions (as specified in CutBlock ) to the real position of the corresponding blocks on the printed Sheet.
|
Values of the BlockName Partition Attributes of the blocks defined by the CutMark Resource. |
||
|
Position of the logical center of the cut mark in the coordinates of the MarkObject that contains this mark. Note that the logical center of the cut mark does not always directly specify the center of the visible cut mark symbol. |
7.2.48 CuttingParams
This Resource describes the parameters of a Cutting Process that uses nested CutBlock Elements as input.
BlockName , RibbonName, SheetName, SignatureName, WebName
|
Defines the number of CutBlock Elements in x and y direction. For example, a 2-up book sawed apart would have NUpSeparation = "2 1" . |
||
|
CutBlock * |
One or several CutBlock Elements can be used to find the Cutting sequence. The CutBlock Elements must not be written if Cut Elements are specified. |
|
|
CutMark * |
CutMark Resources can be used to adapt the theoretical cut positions to the real positions of the corresponding blocks on the Component to be cut. Replaced by Component / Layout in JDF 1.3 and above. |
|
|
Cut * |
Cut Elements describe an individual cut. Cut Elements must not be specified if CutBlock Elements are specified. |
7.2.48.1 Element: Cut
Cut describes one straight cut with an arbitrary tool.
|
Relative starting position of the tool. The RelativeStartPosition is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0 for each component of the XYPair, which specifies the full size of the input Component . |
||
|
Relative working path of the tool beginning at RelativeStartPosition . Since the tools can only work parallel to the edges, one coordinate must be zero. RelativeWorkingPath is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0 for each component of the XYPair, which specifies the full size of the input Component . |
||
|
Starting position of the tool. If both StartPosition and RelativeStartPosition are specified, RelativeStartPosition is ignored. At least one of StartPosition or RelativeStartPosition must be specified. |
||
|
Working path of the tool beginning at StartPosition . Since the tools can only work parallel to the edges, one coordinate must be zero. If both WorkingPath and RelativeWorkingPath are specified, RelativeWorkingPath is ignored. At least one of WorkingPath or RelativeWorkingPath must be specified. |
||
7.2.49 CylinderLayout
Describes the mapping of plates to cylinders on a newspaper-Web Press. This information might be important for prepress systems. For instance, if a system wants to indicate the cylinder position as human readable text onto the plate.
PlateLayout, ProductionRun, Separation
|
Specifies the Device that this CylinderLayout belongs to. |
||
|
Specifies the position of a plate on a cylinder of a newspaper-Web Press. |
||
|
Layout ? |
References the Layout that describes the plates to be mounted. |
7.2.49.1 Element: CylinderPosition
|
Specifies where to mount this plate onto the cylinder. See figure below for details. |
||
|
Specifies whether the plate contains content data or represents a dummy plate. Additionally, it indicates where in the workflow it will be produced. Dummy - Indicates that the plate is a dummy plate. It must be bent by a Bending Process. But it is unlikely to be exposed by an ImageSetting Process. Exposed - Indicates that the plate contains content data and must be exposed by an ImageSetting Process. |
||
|
Specifies, whether a plate has to be produced for a specific Web run or not. Original - indicates that the plate is to be produced specifically for this run. Reuse - indicates that a plate of a previous run will be re-used (same plate position on the Web Press). For instance, a dummy on a specific CylinderPosition can be used in multiple Web runs. |
||
|
Defines a Module with ModuleType = "PrintModule" within the Device specified by CylinderLayout / @DeviceID . In a newspaper-Web Press, "PrintModule" corresponds to a single cylinder. |
In Figure 7-22, the direction of the view is from the plate cylinder towards the paper. If this direction is vectored as the direction of the former module, this is a left-printing spot. Otherwise it is a right-printing spot. If a 'left-printing spot' is considered, 'Side A' is to the left and 'Side B' to the right. And vice versa for a 'right-printing spot'. The plate position in X-dimension starts numbering at Side B. Thus, for the innermost Side B position X = "0" . For the outmost Side A position X = "1" for single-width presses. On double-width presses X = "3" for the outmost Side A position. On triple-width presses X = "5" for the outmost Side A position. Note: The Back and Front side have the same X position on corresponding segments of a Web.
|
The sketch in Figure 7-23 shows a single cylinder of a newspaper-Web Press for a broadSheet production. The numbers indicate Reader Page numbers. The colored dots indicate color separations. Dummy means no content-bearing plates are mounted on this cylinder position. Instead, so called dummy forms are mounted.
|
Example 7-20: CylinderLayout
The following CylinderLayout is an example representation of the cylinder layout as shown in the sketch.
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID = "Bundle" Status = "Waiting"
Type = "CylinderLayoutPreparation" JobPartID = "ID20" Version = "1.4" >
< CylinderLayoutPreparationParams ID = "CL002" Class = "Parameter"
</ CylinderLayoutPreparationParams >
< RunList ID = "R-002" Class = "Parameter" Status = "Available" />
< Device ID = "DEV-001" Manufacturer = "MAN" ModelName = "GEOMAN" Status = "Available"
Class = "Implementation" DeviceID = "DEV-001" >
< Module ModuleIndex = "0" ModuleType = "Folder" ModelName = "Folder 1" >
< Module ModuleIndex = "1" ModuleType = "PrintUnit"
< Module ModuleIndex = "2" SubModuleIndex = "0"
ModuleType = "PrintModule" DescriptiveName = "PM-1" />
< Module ModuleIndex = "3" SubModuleIndex = "1"
ModuleType = "PrintModule" DescriptiveName = "PM-2" />
< Module ModuleIndex = "4" SubModuleIndex = "2"
ModuleType = "PrintModule" DescriptiveName = "PM-3" />
< Module ModuleIndex= "5" SubModuleIndex = "3"
ModuleType = "PrintModule" DescriptiveName = "PM-4" />
< Module ModuleIndex = "6" SubModuleIndex = "4"
ModuleType = "PrintModule" DescriptiveName = "PM-5" />
< Module ModuleIndex = "7" SubModuleIndex = "5"
ModuleType = "PrintModule" DescriptiveName = "PM-6" />
< Module ModuleIndex = "8" SubModuleIndex = "6"
ModuleType = "PrintModule" DescriptiveName = "PM-7" />
< Module ModuleIndex = "9" SubModuleIndex = "7"
ModuleType = "PrintModule" DescriptiveName = "PM-8" />
< Layout ID = "L-001" Class = "Parameter" Status = "Available" />
< CylinderLayout ID = "CL-001" Class = "Parameter" Status = "Available"
PartIDKeys = "WebSetup PlateLayout Separation"
< CylinderLayout WebSetup = "Run-1" >
< CylinderLayout PlateLayout = "PL-001" >
< CylinderLayout Separation = "Yellow" >
< CylinderPosition DeviceModuleIndex = "2" PlatePosition = "0 0"
PlateType = "Exposed" PlateUsage = "Original" />
< CylinderPosition DeviceModuleIndex = "2" PlatePosition = "0 1"
PlateType = "Exposed" PlateUsage = "Original" />
< CylinderLayout PlateLayout = "PL-002" >
< CylinderLayout Separation = "Yellow" >
< CylinderPosition DeviceModuleIndex = "2" PlatePosition = "1 0"
PlateType = "Exposed" PlateUsage = "Original" />
< CylinderPosition DeviceModuleIndex = "2" PlatePosition = "1 1"
PlateType = "Exposed" PlateUsage = "Original" />
< CylinderLayout PlateLayout = "PL-003" >
< CylinderLayout Separation = "HKS57" >
< CylinderPosition DeviceModuleIndex = "2" PlatePosition = "2 0"
PlateType = "Exposed" PlateUsage = "Reuse" />
< CylinderPosition DeviceModuleIndex = "2" PlatePosition = "2 1"
PlateType = "Exposed" PlateUsage = "Reuse" />
< CylinderPosition DeviceModuleIndex = "2" PlatePosition = "3 0"
PlateType = "Dummy" PlateUsage = "Reuse" />
< CylinderPosition DeviceModuleIndex = "2" PlatePosition = "3 1"
PlateType = "Dummy" PlateUsage = "Reuse" />
< DeviceLink Usage = "Input" rRef = "DEV-001" />
< LayoutLink Usage = "Input" rRef = "L-001" />
< RunListLink Usage = "Input" rRef = "R-002" />
< CylinderLayoutPreparationParamsLink Usage = "Input" rRef = "CL002" />
Example 7-21: CylinderLayout: Double-Spread-Page Plate
In case of a double-spread-page plate (or double-truck-page plate) the CylinderPosition MAY be set as:
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="Bundle" Status="Waiting"
Type="CylinderLayoutPreparation" JobPartID="ID20" Version="1.4">
<CylinderLayout ID="CL-001" Class="Parameter" Status="Available"
PartIDKeys="WebSetup PlateLayout Separation"
<!-- PlatePosition (XYPairRangeList)-->
< CylinderPosition DeviceModuleIndex = "2" PlatePosition = "0 0 ~ 1 0"
PlateType = "Exposed" PlateUsage = "Original" />
<Layout ID="L-001" Class="Parameter" Status="Available"/>
<Runlist ID="R-002" Class="Parameter" Status="Available"/>
<CylinderLayoutLink Usage="Output" rRef="CL-001"/>
<LayoutLink Usage="Input" rRef="L-001"/>
<RunlistLink Usage="Input" rRef="R-002"/>
7.2.50 CylinderLayoutPreparationParams
This Resource specifies the parameters of the CylinderLayoutPreparation Process.
|
ProductionPath describes the individual paper path through the different modules of a Web Press. |
7.2.51 DBMergeParams
This Resource specifies the parameters of the DBTemplateMerging Process.
|
Indicates how often to split documents to create a new file. |
||
|
FileSpec ? |
URL of the generated destination file. This is most often a printable file type, (e.g., PDF of PPML). If FileSpec is not specified, DBMergeParams must be a Pipe Resource. |
7.2.52 DBRules
This Resource specifies the rules that are to be applied to convert a database record into a graphic element. It is described by a text element with a human-readable description of the selection rules. For example:
insert the “Age” field behind the birthday;
if income>100,000 use Porsche.gif , else use bicycle.jpeg for image #2.
The internal representation of the mapping of database fields to graphic content within the document template is implementation-dependent. It can vary from fully variable, multi-page, automated document layout to simply inserting some line-feed characters between database records in an address field. Therefore, DBRules is defined as a simple human-readable text element.
DBDocTemplateLayout , Collecting , Gathering , Inserting
|
Comment + |
Human-readable description of the database rules that map database fields to image or text content. |
7.2.53 DBSchema
This Resource specifies the formal structure of a database record, regardless of type. It is encoded as a text element with a human-readable description of the database schema.
DBDocTemplateLayout , Verification
|
Comment + |
7.2.54 DBSelection
This Resource specifies a selection of records from a database.
DBTemplateMerging , Collecting , Gathering , Inserting , Verification
|
Database selection criteria in the native language of the database, (e.g., SQL). |
7.2.55 DeliveryParams
Provides information needed by a Delivery Process. A Delivery Process consists of sending a quantity of a product to a specific location at, in some cases, a specified date and time.
|
Specifies the earliest time after which the delivery is intended to be made. |
||
|
Specifies a delivery method, (e.g., "ExpressMail" or "InterofficeMail" ). Note that it is strongly recommended to use an NMTOKEN compatible string in this Attribute, without blanks. Values include those from: DeliveryIntent /@ Method |
||
|
If "true" , the merchandise is picked up. If "false" , the merchandise is delivered. Replaced with Transfer in JDF 1.2. |
||
|
Specifies the time by which the delivery is intended to be made. |
||
|
The service level of the specific carrier. Values include those from: DeliveryIntent / ServiceLevel |
||
|
Describes the direction and responsibility of the transfer. BuyerToPrinterDeliver - The DeliveryIntent describes an input to the Job, (e.g., a CD for inserting, a preprinted cover, etc.). In this case, the buyer delivers the merchandise to the printer. The printer can choose to specify in the quote a special Contact [contains (@ ContactTypes , "Delivery" ]. This Contact specifies where the buyer is to send the merchandise. BuyerToPrinterPickup - The DeliveryIntent describes an input to the Job, (e.g., a CD for inserting, a preprinted cover, etc.). In this case, the printer picks up the merchandise. The Contact [contains (@ ContactTypes , "Pickup" )] specifies where the printer is to pick up the merchandise. PrinterToBuyerDeliver - The DeliveryIntent describes an output of the Job. In this, case the printer delivers the merchandise to the buyer. The Contact [contains (@ ContactTypes , "Delivery" )] specifies where the printer is to send the merchandise. PrinterToBuyerPickup - the DeliveryIntent describes an output of the Job. In this case, the buyer picks up the merchandise. The printer can choose to specify in the quote a special Contact [contains (@ ContactTypes , "Pickup" )]. This Contact specifies where the buyer is to pick up the merchandise. |
||
|
Company ? |
Address and further information of the addressee. In JDF 1.1 and beyond, use Contact / Company |
|
|
Contact * |
Address and further information of the Contact responsible for this delivery. |
|
|
Drop + |
7.2.55.1 Element: Drop
|
Specified the earliest time after which the delivery is to be made. Default value is from: DeliveryIntent /@ Earliest. |
||
|
Specifies a delivery method, (e.g., "ExpressMail" or "InterofficeMail" ). Note that it is strongly recommended to use an NMTOKEN compatible string without blank spaces in this Attribute. Default value is from: DeliveryParams /@ Method Values include those from: DeliveryIntent /@ Method |
||
|
If "true" , the merchandise is picked up. If "false" , the merchandise is delivered. Default = DeliveryParams /@ Pickup . Replaced with Transfer in JDF 1.2. |
||
|
Specifies the time by which the delivery is intended to be made. Default value is from: DeliveryParams /@ Required |
||
|
The service level of the specific carrier. Default value is from: DeliveryParams /@ ServiceLevel Values include those from: DeliveryParams /@ ServiceLevel |
||
|
The string that can help in tracking the delivery. The value of the TrackingID Attribute will depend on the carrier chosen to ship the products. |
||
|
Describes the direction and responsibility of the transfer. Default value is from: DeliveryParams /@ Transfer . Values are from: DeliveryParams /@Tra nsfer. |
||
|
Company ? |
Address and further information of the addressee. Defaults to the value of Company specified in the root DeliveryParams Resource. |
|
|
Contact * |
Address and further information of the Contact responsible for this delivery. Default = DeliveryParams / Contact . |
|
|
DropItem + |
A Drop may consist of multiple products, which are represented by their respective PhysicalResource Elements. Each DropItem describes an individual Resource that is part of this Drop . |
7.2.55.2 Element: DropItem
|
Actual amount of items delivered in this drop. Note that this logs the information after the fact in a way that is similar to an Audit . ActualAmount was placed here because it is very difficult to map the DeliveryParams structure of individual Drop and DropItem Elements to ResourceLink and Audit Elements. |
||
|
Actual TotalAmount of items delivered in this drop. Note that this logs the information after the fact in a way that is similar to an Audit . ActualTotalAmount was placed here because it is very difficult to map the DeliveryParams structure of individual Drop and DropItem Elements to ResourceLink and Audit Elements. |
||
|
Specifies the number of Physical Resource s ordered. If Amount is not specified, defaults to the total amount of the Resource that is referenced by PhysicalResource . |
||
|
Total amount of individual items delivered in this drop. The TotalAmount and Amount differ if the PhysicalResource is a Bundle of multiple Resources. The Amount specifies the number of Bundle s (e.g., boxes, pallets etc.). Whereas TotalAmount specifies the number of final products, (e.g., books, magazines etc.). |
||
|
Total dimensions in points of all individual items including packaging delivered in this drop. |
||
|
Total volume in liters of all individual items including packaging delivered in this drop. |
||
|
Total weight in gram of all individual items including packaging delivered in this drop. |
||
|
The string that can help in tracking the delivery. The value of the TrackingID Attribute will depend on the carrier chosen to ship the products. Defaults to Drop /@ TrackingID . |
||
|
Unit of measurement for the Amount of the Resource that is referenced by PhysicalResource . Default value is from: PhysicalResource /@ Unit |
||
|
Description of the individual item to be delivered. It can be any kind of Physical Resource . This was Component prior to JDF 1.2. |
7.2.56 DensityMeasuringField
This Resource contains information about a density measuring field.
ColorControlStrip , Layout / MarkObject
|
Position of the center of the density measuring field in the coordinates of the MarkObject that contains this mark. If the measuring field is defined within a ColorControlStrip , Center refers to the rectangle defined by Center and Size of the ColorControlStrip . |
||
|
Density value for each process color measured with filter. The data type was modified to NumberList in JDF 1.1A in order to accommodate density values >1.0. The sequence of colors remains C M Y K , as in the data type CMYKColor. |
||
|
Reference to a Separation that this applies DensityMeasuringField to. When DensityMeasuringField is used as an Element, it is a standard Attribute, otherwise when DensityMeasuringField is used as a Resource, Separation must be defined as a Separation Partition Key. |
||
|
Upper and lower magenta measurement limits (in density units). |
||
|
Upper and lower yellow measurement limits (in density units). |
||
|
Upper and lower black measurement limits (in density units). |
||
|
Detailed description of the measurement conditions for color measurements. |
7.2.57 DevelopingParams
DevelopingParams specifies information about the chemical and physical properties of the developing and fixing process for film and plates. Includes details of preheating, postbaking and postexposure.
- Preheating is necessary for negative working plates. It hardens the exposed areas of the plate to make it durable for the following developing process. The stability and uniformity of the preheat temperature influence the evenness of tints and the run length of the plate on press.
- Postbaking is an optional process of heating that is applied to most polymer plates to enhance the run length of the plate. A factor 5 to 10 can be gained compared to plates that are not postbaked.
- Postexposure is an optional exposure process for photopolymer plates to enhance the run length of the plate. A factor of 5 to 10 can be gained compared with plates that are not postexposed.
Note: Postbaking and postexposure are mutually exclusive.
7.2.58 Device
Information about a specific Device. This can include information about the Devices capabilities. For more information, see Section 3.8.5.3, “Implementation Resource” and Section 4.8, “Capability and Constraint Definitions”.
PhaseTime , DeviceFilter , IDInfo , Occupation , DeviceInfo , Queue , QueueFilter , DieLayout , DieLayoutProductionParams / ConvertingConfig , InkZoneCalculationParams , PrintCondition , RollStand , StrippingParams
|
Manufacturer family type ID. The DeviceFamily is replaced by the appropriate ModelXXX Attributes in this list. |
||
|
Name of the Device. This is a unique name within the workflow. DeviceID must be the same over time for a specific Device instance, (i.e., must survive reboots). If the Device sends JMF Messages, this value must also used for JMF / @SenderID . For UPNP Devices, this must match UPNP:UDN. See [UPNP] . DeviceID need not be specified when Device is used as a filter to specify a set of Devices. |
||
|
Manufacturer type ID, including a revision stamp. Type of the Device. Used for grouping and filtering of Devices |
||
|
Defines a directory where the URLs that are associated with this Device can be located. If Directory is specified, it must be an Absolute URI [RFC3986] that implicitly also specifies a Base URI which is used to resolve any relative URL of Device . See Appendix J, “Resolving RunList/@Directory and FileSpec/@URL URI References” and [FileURL] . |
||
|
Deprecation note: starting with JDF 1.4, use DescriptiveName . |
||
|
CIP4 Interoperability Conformance Specification (ICS) Versions that this Device complies with. Values include those from: JDF /@ ICSVersions (Table 3-5, “JDF Node”). |
||
|
URL where, by default, the Device will post JDF output Job tickets that are aborted or in error and when NodeInfo /@ TargetRoute is not specified. If JDFErrorURL is specified in the "file" scheme, it MUST specify a directory. If not specified, JDFErrorURL defaults to the value of JDFOutputURL . |
||
|
URL where, by default, the Device can accept JDF input Job tickets. If JDFInputURL is specified in the "file" scheme, it MUST specify a directory. The persistence of JDF tickets in this location is implementation dependent. If not specified, the Device does not accept JDF without a JMF SubmitQueueEntry . |
||
|
URL where, by default, the Device will post JDF output Job tickets that are successfully completed and when NodeInfo /@ TargetRoute is not specified. If JDFOutputURL is specified in the "file" scheme, it MUST specify a directory. |
||
|
Whitespace separated list of supported JDF versions that this Device supports, (e.g., "1.0 1.1" specifies that both the 1.0 and 1.1 version are supported). |
||
|
ID of the Controller will process JMF Messages for the Device. This corresponds to the SenderID Attribute that is specified for the Device in JMF Messages. If a Device emits it's own JMF Messages, this value must match the DeviceID . |
||
|
URL of the Device port that will accept JMF Messages. A Controller that manages a Device may specify its own JMFURL when responding to KnownDevices Messages. This is how a Controller inserts itself as the manager for a Device. |
||
|
A list of all language codes supported by the Device for localization. If not specified, then the Device supports no localizations. |
||
|
PresentationURL specifies a URL to a Device-provided user interface for configuration, status, etc. For instance, if the Device has an embedded Web server, this is a URL to the configuration page hosted on that Web server. |
||
|
URL of the Device port that will accept JMF Messages via the "https" protocol. |
||
|
Universal Product Code for the Device. A 12-digit, all-numeric code that identifies the consumer package. Managed by the Uniform Code. |
||
|
Description of the capabilities of the Device. The DeviceCap Elements are combined with a logical OR, (i.e., if a JDF resides within any parameter space defined by a DeviceCap , the Device can process the Job). For details see Section 7.3, “Device Capability Definitions”. |
||
|
List of locations of icons that can be used to represent the Device. |
||
|
Location ? |
||
|
Module * |
Individual Modules that are represented by this Device . |
7.2.58.1 Element: IconList
The IconList is a list of individual icon descriptions.
|
Icon + |
7.2.58.2 Element: Icon
An Icon represents a Device in the user interface.
|
Definition of the Status of the Device that this Icon represents. Any combination of values are allowed: Default value is: a list of all values (i.e. no limit on Icon us e). Unknown - No link to the Device exists Note: The meaning of the individual enumerations is described in the DeviceInfo Message Element. See Section 5.8.3, “KnownDevices”. |
||
7.2.58.3 Element: Module
A Module represents a physical Machine or part of a Device .
|
Name of the Module. This is a unique identifier within the workflow. ModuleID must be the same over time for a specific Device instance, (i.e., must survive reboots). At least one of ModuleID or ModuleIndex must be specified. If multiple logical Devices share a physical Module , ModuleID must be identical. ModuleID should be used to specify Machines that comprise a Device . |
||
|
Zero-based index of the module within the Machine. This index used to reference an individual Module. At least one of ModuleID or ModuleIndex must be specified . ModuleIndex should be used to specify identical modules, e.g., print modules in a complex Device. |
||
|
Type of Module . Values include those from: Section C.2, “ModuleType Supported Strings” . Note: the allowed values depend on the type of Device. Each type of Device has a separate table of values. |
||
|
Zero-based index of the Module in the unit as specified by the parent Module . must not be specified if Module is a direct child of Device . |
||
|
Module * |
7.2.59 DeviceMark
Promoted from Subelement status in the Layout Resource with new Attributes defined below.
Layout / MarkObject , LayoutPreparationParams , LayoutPreparationParams / PageCell
|
Anchor point within this DeviceMark that MarkObject /@ CTM refers to. |
||
|
The name of the font that is to be used for the DeviceMark . |
||
|
The size of the font that is to be used for the DeviceMark , in points ≥ 0. Modification note: starting with JDF 1.4, the data type is no longer integer. |
||
|
Values are from: StripMark /@ HorizontalFitPolicy |
||
|
Description of the preferred DeviceMark justification. Interpreted in context of the MarkOrientation . |
||
|
Description of the preferred DeviceMark offset. Interpreted in context of the Device dependent default position in the coordinate system defined by MarkOrientation . |
||
|
Description of the preferred DeviceMark orientation. |
||
|
Description of the preferred DeviceMark position. |
||
|
Values are from: StripMark /@ VerticalFitPolicy |
||
|
Reproduction parameters for Barcodes specified in the parent MarkObject / IdentificationField . |
7.2.60 DeviceNSpace
Note: DeviceNSpace was elevated to a Resource in JDF 1.2. The DeviceNSpace can be used in several ways. For example, defining the specific colorants of a DeviceNSpace :
- ColorantControl / ColorPool /@ ColorantSetName matches ColorantControl / DeviceNSpace /@ Name , and a:
- ColorantControl / ColorPool / Color Resource (with correct Name of colorant and other defining Attributes) exists for each colorant of the DeviceNSpace as given in:
- ColorantControl / DeviceNSpace / SeparationSpec /@ Name
For example, defining a single colorant in terms of its values in a DeviceNSpace :
- ColorantControl / ColorantParams names a colorant, (e.g., a Pantone spot color).
- ColorantControl / DeviceNSpace names a DeviceN color space, which then the
- ColorantControl / ColorPool /@ ColorantSetName matches, and then the corresponding
- ColorantControl / ColorPool / Color / DeviceNSpace /@ ColorList Attribute gives the set of DeviceNSpace colorant percent values necessary to construct the,
- ColorantControl /@ ColorantParams colorant (also named ColorantControl / ColorPool / Color /@ Name ) in using DeviceNSpace colorants.
ColorantControl , ColorSpaceConversionOp
|
Ordered list of colorant names that define the DeviceN color space. Note that these colorants must be specified in a corresponding ColorantParams Element of the ColorantControl or be implied by ProcessColorModel . In other words, they must be real, physical colorants. |
7.2.61 DieLayout
DieLayout represents a die layout described in an external file. This Resource is also used as the input for the actual die making process and is also used in Stripping . The external file is by preference a DDES3 file (ANSI® IT8.6-2002 ). The usage of other files like CFF2 , DDES2 , DXF or proprietary formats is not excluded but may have a negative impact on interoperability.
BinderySignature , ShapeCuttingParams
DieDesign , DieLayoutProduction
|
Determines the die side for which the DieLayout is made. Up - the DieLayout is made with the knifes pointing upwards. Down - the DieLayout is made with the knifes pointing downwards. |
||
|
Determines the printing side for which the DieLayout is made. |
||
|
Indicates if some of the structural designs are oriented cross grain/flute in the layout. |
||
|
The percent of the material that is wasted. Inner waste i.e. cut out windows are not included in the waste. |
||
|
Device * |
The Devices for which this DieLayout was made (printing press and die cutter). Typically only the type of Device would be used e.g. the model of the die cutter. |
|
|
FileSpec ? |
||
|
Media ? |
Media for which this DieLayout was intended. The Media description defines important design parameters as the type of Media , dimensions, grain direction or flute direction. |
|
|
Elements describing the length of die rules for the different types of rules. Each RuleLength Element describes the accumulated length of all rules of a certain type. |
||
|
Station * |
Description of the stations in a DieLayout . One Station produces one shape. |
7.2.61.1 Element: RuleLength
|
a number between "0" and "999" corresponding to a line type as defined in DDES. |
||
|
Accumulated length of the rules of this type in the DieLayout (pt). |
7.2.61.2 Element: Station
|
The list of AssemblyIDs of the graphic elements that are processed by this Station . |
||
|
The number of stations in the DieLayout with this StationName . |
||
|
The name of the 1-up design in the DieLayout . |
||
|
ShapeDef ? |
The ShapeDef corresponding to this station in the DieLayout . |
7.2.62 DieLayoutProductionParams
Parameters for the die layout.
|
Determines if the Process runs in estimate mode or not. When in estimate mode multiple solutions are generated. |
||
|
A ConvertingConfig Element describes a range of Sheet sizes that can be taken into account to create a new DieLayout . Typically a ConvertingConfig will correspond to 1 (printing press, die cutter) combination. |
||
|
Step and repeat parameters for a ShapeDef .There is either a single RepeatDesc giving the parameters for all ShapeDef Resources at the input or there is exactly 1 RepeatDesc per ShapeDef in the input in which case the sequence of both determines which RepeatDesc should be used for a ShapeDef . |
7.2.62.1 Element: ConvertingConfig
The ConvertingConfig Element describes a range of Sheet sizes.
|
Device * |
The target devices (printing press and die cutter) corresponding to this configuration. Typically only the type of Device would be used e.g. the model of the die cutter. |
7.2.62.2 Element: RepeatDesc
The RepeatDesc Element describes the layout specs for a ShapeDef .
|
Allowed methods to rotate structural designs in with respect to grain/flute. MinorGrain - device dependent small rotations that retain the general grain direction, e.g. +/- 10˚ CrossGrain - Cross grain rotations, e.g. 90˚ are acceptable. |
||
|
Secondary gutter between columns. When the LayoutStyle = "Reverse2ndColumn" , the gutter between columns (2n+1) and (2n+2) is GutterX and between columns (2n+2) and (2n+3) is GutterX2 . When GutterX2 is not specified GutterX2 = GutterX . See Figure 7-30, “RepeatDesc/@GutterX2 and @GutterY2: Secondary Gutters”. |
||
|
Secondary gutter between rows. When the LayoutStyle = "Reverse2ndRow" the gutter between rows (2n+1) and (2n+2) is GutterY and between rows (2n+2) and (2n+3) GutterY2 . When GutterY2 is not specified GutterY2 = GutterY . See Figure 7-30, “RepeatDesc/@GutterX2 and @GutterY2: Secondary Gutters”. |
||
|
The allowed styles for the Layout Note: for diagrams of the above values, see Figure 7-24, “Basic Shape for RepeatDesc/@LayoutStyle Examples” and the following five figures |
||
|
The order quantity for the 1-up for which this layout will be optimized. This information needs to be present when a Layout is being made for more than 1 ShapeDef . |
||
|
If true, the print bleed defined in the structural design is used to calculate the layout. If false, the outer cut is used. |
The following Figure shows the basic shape for subsequent Figures. that relate to RepeatDesc .
|
|
In the following Figure, 1-ups on even rows are rotated 180 degrees. Even rows are shifted horizontally and vertically to obtain optimal nesting.
|
In the following Figure, 1-ups on even rows are rotated 180 degrees. Even rows are shifted vertically to obtain optimal nesting. The even rows are not shifted horizontally. (Left and right edges are aligned between rows)
|
In the following Figure, 1-ups on even columns are rotated 180 degrees. Even columns are shifted vertically and horizontally to obtain optimal nesting.
|
In the following Figure, 1-ups on even columns are rotated 180 degrees. Even columns are shifted horizontally to obtain optimal nesting. No vertical shifting of even columns is done (top and bottom edges are aligned between columns).
|
In the following Figure, LayoutStyle = "Reverse2ndRow" , GutterY = "15" , GutterY2 = "0" .
|
7.2.63 DigitalDeliveryParams
This Resource specifies the parameters of the DigitalDelivery Process.
|
Describes which side activates the delivery. Push - The artwork will be sent (the source end is active). Pull - The artwork will be retrieved (the destination end is active). |
||
|
Identifies the delivery method. NetworkCopy - This includes LAN and VPN. WebServer - Upload / Download from HTTP / FTP server. |
||
|
Contact * |
Source and destination address for the transfer of the artwork. The destination delivery address is specified as the Contact [contains (@ ContactTypes , "Delivery" )]/ ComChannel . Exactly one such Contact must be specified per destination. If multiple delivery destinations are specified within one DigitalDelivery Process, such a Contact must be Partitioned with the Partition Key "Location" . If the output RunList completely specifies the destination, a Contact [contains (@ ContactTypes , "Delivery" )] should be omitted. This is generally the case if Method = "NetworkCopy" or "WebServer" . A Contact [contains (@ ContactTypes , "Sender" )] specifies the source address. |
Compression & Encoding of the transferred files:
In order to instruct a digital delivery Device to compress or encode the files one can use the input and output RunList with FileSpec /@ Compression Attribute, even if no URL is specified. See Section N.7, “DigitalDelivery Examples” for a set of examples.
7.2.64 DigitalMedia
This Resource represents a processed removable digital media-based Handling Resource such as tape or removable disk.
ArtDeliveryIntent / ArtDelivery
|
Exabyte - Exabyte tape backup media. HardDrive - Removable hard drives from a rack. Jaz - Jaz removable disk drive. Optical - Optical removable disk drive. Excluding CDs and DVDs. Tape - Tape backup media. Use only when the explicit tape type is not listed here. |
||
|
The digital media type details -- could be vendor or model name. For example: " 8mm " or "VHS" for tape media. |
||
|
RunList ? |
Link to the relevant files on the media. The URLs specified in RunList / LayoutElement / FileSpec /@ URL should be relative paths to the media's mount point. |
7.2.65 DigitalPrintingParams
This Resource contains Attributes and Elements used in executing the DigitalPrinting Process. The PrintingType Attribute in this Resource defines two types of printing: "SheetFed" and "WebFed" . The principal difference between them is the shape of the paper each is equipped to accept. Presses that execute "WebFed" Processes use substrates that are continuous and cut after printing is accomplished. Most newspapers are printed on Web Presses. "SheetFed" printing, on the other hand, accepts precut substrates.
7.2.65.1 Coordinate systems in DigitalPrinting
Figure 2-11 in Section 2.5, “Coordinate Systems in JDF” defines the coordinate system for ConventionalPrinting and DigitalPrinting . Note that the paper feed direction of the idealized Process is towards the X-axis which corresponds to bottom edge first.
BlockName , DocRunIndex, DocSheetIndex, PartVersion, Run, RunIndex, RunTags, DocTags, PageTags, SetTags, SheetIndex, Separation, SheetName, Side, SignatureName, DocIndex
|
Determines the sequencing of the Sheets in the document and the documents in the Job when multiple copies of a document or a Job are requested as output. Document copies can be requested by specifying RunList /@ DocCopies and Job copies can be requested by specifying the output Component Amount . None - Do not collate Sheets in the document or document(s) in the Job. Sheet - Collate the Sheets in each document; do not collate the documents in the Job. The result of "Sheet" and "SheetAndSet" is the same when there is one document in the set. The result of "Sheet" and "SheetSetAndJob" is the same when there is one document in the set and one set in the Job. SheetAndSet - Collate the Sheets in the document and collate the documents in the set. Do not collate the sets in the Job. The result of "SheetAndSet" and "SheetSetAndJob" is the same when there is one set in the Job. SheetSetAndJob - Collate the Sheets in the document and collate the documents in the set and collate the sets in the Job. Example: two documents, A and B, each have two Sheets, A1, A2 and B1, B2 . The number of document copies requested is one for both documents and the number of Job copies requested is three ( Component /@ Amount = 3). The Job contains no Document Set boundaries. If Collate = "None" , the Sheet order will be: If Collate = "Sheet" , the Sheet order will be: If Collate = "SheetAndSet" or "SheetSetAndJob" , the Sheet order will be: |
||
|
If greater than zero (>0), a set of proofs is directly produced and subsequently an approval might be given by a person (e.g., the customer, foreman or floor manager) shortly after the first final-quality printed Sheet is printed. Approval is needed for the actual print run, but not for setup. If the DigitalPrinting Process is waiting for a DirectProofAmount , the JDF Node’s Status is switched to "Stopped" with the StatusDetails = "WaitForApproval" . |
||
|
The width in points of the bottom margin measured inward from the edge of the media (before trimming if any) with respect to the idealized Process coordinate system of the DigitalPrinting Process. The DigitalPrinting Process must put marks up to, but not in, the non-printable margin area. The Media ’s origin is unaffected by NonPrintableMarginBottom . These margins are independent of the PDL content. |
||
|
Same as NonPrintableMarginBottom except for the left margin. |
||
|
Same as NonPrintableMarginBottom except for the right margin. |
||
|
Specifies the bin to which the finished document is to be output. Values include those from: Table C-21, “Input Tray and Output Bin Names” . |
||
|
Indicates how pages are to be delivered to the output bin or finisher. Note: these values refer to the orientation of the entire stack being output from the press, not individual sheets. For example, "SameOrderFaceDown" means that the stack can be picked up and turned over to find the output sheets in the same order as the input RunList with the first page on top facing up FanFold - The output is alternating face-up, face down. SameOrderFaceUp - Order as defined by the RunList , with the “ Front ” sides of the media up and the first Sheet on top. SameOrderFaceDown - Order as defined by the RunList , with the “ Front ” sides of the media down and the first Sheet on the bottom. ReverseOrderFaceUp - Sheet order reversed compared to SameOrderFaceUp , with the Front sides of the media up and the last Sheet on top. ReverseOrderFaceDown - Sheet order reversed compared to SameOrderFaceDown , with the Front sides of the media down and the last Sheet on the bottom. |
||
|
ContinuousFed - connected Sheets including fan fold. New in JDF 1.2 SheetFed |
||
|
Indicates how pages are to be delivered to the output bin or finisher. High - Highest quality available on the printer. Normal - The default quality provided by the printer. Draft - Lowest quality available on the printer Deprecation note: starting with JDF 1.1, use InterpretingParams /@ PrintQuality |
||
|
Lay of input media. Reference edge of where paper is placed in feeder. |
||
|
Indicates whether the ByteMap must be imaged on one or both sides of the media. If the RunList ( Surfaces ) input to DigitalPrinting is Partitioned by Side (either explicitly or implicitly using the RunList /@ SheetSides Attribute), then the input RunList provides a binding of front and back surfaces to sheets. If @ Sides = "OneSidedFront" or "OneSidedBack" , then that binding is ignored and one surface is imaged per sheet. If the RunList ( Surfaces ) does not provide the binding of surfaces to sides, then the Sides Attribute specifies the binding to be applied. When a different value for this Attribute is encountered, it must force a new Sheet. However, when the same value for this Attribute is restated for consecutive pages, it is the same as if that restatement was not present. Values are from: LayoutPreparationParams /@ Sides |
||
|
Details of the direct approval Process, when DirectProofAmount > 0. |
||
|
Describes the preprocessed media to be used. Different Media and/or Component Resources may be specified in different Partition leaves to enable content-driven input Media selection. At most one of Media or Component must be specified per Partition. |
||
|
Describes how individual components are separated from one another in the output bin. |
||
|
Ink ? |
If present indicates that overcoating is to be applied to the surface(s) of printed Sheets and specifies the ink to be used for overcoating. Overcoating ink must be applied after imaging colorants have been printed. Note: for selective image-wise overcoating (e.g., spot varnishing) a separate separation utilizing overcoating ink must be specified. Deprecation note: starting with JDF 1.4, use the Varnishing Process. |
|
|
Media ? |
Describes the media to be used. Different Media and/or Component Resources may be specified in different Partition leaves to enable content driven input Media selection. At most one of Media and Component must be specified per Partition. |
|
|
Describes the media to be used. At most one of MediaSource and Component must be specified. Replaced with Media in JDF 1.1. |
7.2.66 Disjointing
The Disjointing Resource describes how individual components are separated from one another on a stack.
Component , DigitalPrintingParams , GatheringParams , StackingParams
|
Offset dimension in X and Y dimensions that separates the components. |
||
|
The number of components that are shifted in OffsetDirection simultaneously. |
||
|
Offset-shift action for the first component. A component can be offset to one of two positions--left or right. Alternate - The position of the first component is opposite to the position of the previous component and subsequent components are each offset to alternating positions. For example, if the last item in the stack was positioned to the right then the subsequent items will be positioned to the left, right, left, right and so on. Left - Offset consecutive components sideways to the left, next to the right. None - Do not offset consecutive components. The position of all components is the same as the position of the previous component. Right - Offset consecutive components sideways to the right, next to the left. |
||
|
Expansion of the overfold of a Sheet. This Attribute is needed for the Inserting or other postpress Processes. Moved to Component . |
||
|
Marks that identify the range of Sheets to be used in a Process. A scanner will scan the Sheets and detect a component boundary by scanning a mark (e.g., a bar code) that matches the description in the IdentificationField Element. |
||
|
Some kind of physical marker (e.g., a paper strip or a yellow paper Sheet) that separates the components. |
7.2.67 Disposition
This Element describes how long an asset should be maintained by a Device. The Device will perform an action defined by Disposition /@ DispositionAction when a “disposition time” occurs. Disposition time is defined either as:
Until <= "Disposition time" <= Until + ExtraDuration
ProcessCompleteTime+MinDuration <= "Disposition time" <=
ProcessCompleteTime+MinDuration+ExtraDuration
ResourcePullParams , QueueSubmissionParams , SubmitQueueEntry / QueueSubmissionParams , FileSpec , RunList
|
Delete - The asset is deleted when disposition time occurs. Archive - The asset is archived when disposition time occurs. |
||
|
Specifies the usage of the asset by the Process. Default behavior: Disposition applies to all Processes that link to the Disposition Resource (if DispositionUsage not specified). Input - Disposition applies only to Processes that use the asset as an Input Resource. Output - Disposition applies only to Processes that use the asset as an Output Resource. |
||
|
Indicates the maximum duration that the Device is allowed to retain the asset after the time specified by MinDuration or Until . If ExtraDuration, MinDuration and Until are all unspecified, the asset is retained for a system specified time. |
||
|
Indicates the minimum duration that the Device should retain the asset after the Process that uses the asset completes. |
||
|
Value between 0 and 100 that specifies the order in which assets are deleted or archived when the values of ExtraDuration , MinDuration and Until cannot be honored, (e.g., when local storage runs low). Assets with Priority = "0" will be deleted first. |
||
|
Indicates an absolute point in time when the Device or application should stop the asset retention. If Until is specified, MinDuration must be ignored. |
7.2.68 DividingParams
Since the Dividing Process has been replaced by Cutting , this Resource is no longer needed. See Section P.4.5, “DividingParams” for details of this deprecated Resource.
7.2.69 ElementColorParams
This Resource provides a container for color management related metadata applicable to a LayoutElement .
ContentList / ContentData , LayoutElement , PageList , PageList / PageData
|
Identifies the preferred ICC color management system to use when performing color transformations on the particular LayoutElement . When specified, this Attribute overrides any default selection of a color management system by an application and overrides the “CMM Type” value (bytes 4-7 of an ICC Profile Header) in any of the Job related ICC profiles. This string Attribute Value identifies the manufacturer of the preferred CMM and must match one of the registered four-character ICC CMM Type values. Values include those from: the ICC Manufacturer’s Signature Registry at http://www.color.org . |
||
|
This Attribute specifies the usage of the output intent profile or specified printing condition from the PDL. PDLActual - The embedded PDL output printing condition defines the actual output intent profile, (e.g., the final press output). PDLReference - The embedded PDL output printing condition defines the reference output intent profile, (e.g., the press profile for proofing). IgnorePDL - The embedded ICC output profile is incorrect and is to be ignored. |
||
|
A Resource that provides controls for the automated selection of overprinting of black text or graphics. |
||
|
Each Resource instance specifies a replacement colorant name string to be used instead of one or more named colorant strings found in the Layout Resource. Multiple ColorantAlias elements with identical values of ColorantAlias /@ ReplacementColorantName MUST NOT be specified in the same ElementColorParams resource context. |
||
|
List of ColorSpaceConversionOp Subelements, each of which identifies a type of object, defines the source color space for that type of object, and specifies the behavior of the conversion operation for that type of object. If not present, the default conversion behavior is derived from ColorStandard . ColorSpaceConversionOp /@ Operation is ignored in the context of ElementColorParams . |
||
|
FileSpec ( ActualOutputProfile ) ? |
A FileSpec Resource pointing to an ICC profile that describes the characterization of an actual output target Device. |
|
|
FileSpec ( ReferenceOutputProfile ) ? |
A FileSpec Resource pointing to an ICC profile that describes a reference output print condition behavior that is to be simulated as a part of a requested color transformation. This profile corresponds to the output intent contained in a PDF/X file. It should be a specific implementation of ColorIntent /@ ColorStandard . |
7.2.70 EmbossingParams
This Resource contains Attributes and Elements used in executing the Embossing Process. The Embossing can also be used to model a foil stamping Process.
BlockName , RibbonName , SheetName , SignatureName , WebName
|
Emboss * |
One Emboss Element is specified for each impression. |
7.2.70.1 Element: Emboss
|
Both - Both debossing and embossing in one stamp. Flat - The embossing foil is applied flat. Used for foil stamping. New in JDF 1.3 |
||
|
The angle of a beveled edge in degrees. Typical values are an angle of: 30, 40, 45, 50 or 60 degrees. If EdgeAngle is specified, EdgeShape = Beveled must be specified. |
||
|
The transition between the embossed surface and the surrounding media can be rounded or beveled (angled). |
||
|
BlindEmbossing - Embossed forms that are not inked or foiled. The color of the image is the same as the paper. Braille - 6 dot Braille embossing. Note: "Braille" was added to JDF 1.3 Errata. New in JDF 1.3 EmbossedFinish - The overall design or pattern impressed in laminated paper when passed between metal rolls engraved with the desired pattern. Produced on a special embossing to create finishes such as linen. FoilEmbossing - Combines embossing with foil stamping in one single impression. FoilStamping - Using a heated die to place a metallic or pigmented image from a coated foil on the paper. RegisteredEmbossing - Creates an embossed image that exactly registers to a printed image. |
||
|
The height of the levels. This value specifies the vertical distance between the highest and lowest point of the stamp, regardless of the value of Direction . |
||
|
Position of the lower left corner of the bounding box of the embossed image in the coordinate system of the Component . |
||
|
If EmbossingType = "Braille" , IdentificationField describes the content of the Braille Element. |
||
|
Media ? |
If the EmbossingType = "FoilEmbossing" or "FailStamping" , Media describes the foil. |
|
|
Tool ? |
The tool used to make the embossing described by this Element. |
7.2.71 Employee
Information about a specific Device or Machine operator (see Section 3.8.5.3, “Implementation Resource”). Employee is also used to describe the contact person who is responsible for executing a Node, as defined in NodeInfo .
Abstract Audit , Notification , PhaseTime , ModulePhase , JMF , Message , Occupation , DeviceInfo , ModuleStatus , ContentList / ContentData / ContentMetadata , NodeInfo
|
Defines the list of roles that the employee fills. Apprentice - Employee that is in training, ( “Auszubildender” / “Auszubildende” in German). Assistant - Assistant operator. Craftsman - Trained employee, ( “Geselle” / “Facharbeiter” in German). CSR - Customer Service Representative Master - Highly trained employee, ( “Meister” in German). ShiftLeader - The leader of the shift. StandBy - Employee who is allocated to a specific task on demand. New in JDF 1.4 |
||
|
Person ? |
Describes the employee. If no Person Resource is specified, the Employee Resource represents any employee who fulfills the selection criteria. |
7.2.72 EndSheetGluingParams
This Resource describes the Attributes and Elements used in executing the EndSheetGluing Process.
|
EndSheet ( Front ) |
Information about the front-end Sheet. The Side Attribute of this Element must be "Front" . |
|
|
EndSheet ( Back ) |
Information about the back-end Sheet. The Side Attribute of this Element must be "Back"” . |
7.2.72.1 Element: EndSheet
|
Offset of end Sheet in X and Y direction. In JDF 1.2 and beyond, Offset is implied by the Transformation matrix in ResourceLink / @Transformation of the EndSheet Element’s ComponentLink . |
||
|
The process coordinate system is defined as follows: The Y-axis is aligned with the binding edge of the book block. It increases from the registered edge to the edge opposite to the registered edge. The X-axis is aligned with the registered edge. It increases from the binding edge to the edge opposite the binding edge, (i.e., the product front edge).
7.2.73 ExposedMedia
This Resource represents a processed Media -based Handling Resource such as film, plate or paper proof. It is also used as an Input Resource for the Scanning Process.
ArtDeliveryIntent / ArtDelivery
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, Separation , SheetName , Side , SignatureName , TileID , WebName
Bending , ContactCopying , ConventionalPrinting , DigitalPrinting , ImageSetting , PreviewGeneration , Scanning , Varnishing
Bending , ContactCopying , ImageSetting
|
List of the indices of the PageData Elements of the PageList specified in this ExposedMedia . |
||
|
Specifies whether a plate is exposed or a dummy plate. Exposed - The plate has been imaged. Dummy - Specifies a dummy plate that has not been imaged. Usually, dummy plates are only needed on newspaper-Web Presses. |
||
|
When this ExposedMedia specifies a proof, ProofName is the name of the ProofingIntent / ProofItem that specified this proof in the Product Intent section. |
||
|
This Attribute is present if the ExposedMedia Resource describes a proof. None - Not a proof or the quality is unknown. Deprecated in JDF 1.2 Halftone - Halftones are emulated. |
||
|
None - Not a proof or the type is unknown. Deprecated in JDF 1.2 |
||
|
Name of the registration punch scheme. |
||
|
FileSpec ( OutputProfile ) ? |
A FileSpec Resource pointing to an ICC profile that describes the output Process for which this media was exposed. |
|
|
PageList ? |
Specification of page metadata for pages described by this ExposedMedia . |
|
7.2.74 ExternalImpositionTemplate
ExternalImpositionTemplate specifies a reference to an external imposition template.
LayoutPreparationParams , StrippingParams
|
A reference to a file that contains an external imposition template in a private (non-JDF) format. |
7.2.75 FeedingParams
The parameters for any JDF Feeder processing Device.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, Separation , SheetName , Side , SignatureName , TileID , WebName
|
Feeder * |
Defines the specifics of an individual Feeder . If a Component or Media from the Input Resource list is not referenced from a Feeder in this list, a system defined Feeder will be used. |
|
|
Defines the collating sequence of the input Component (s). If a CollatingItem is not defined, then one Component in the order of input ResourceLink list is consumed. |
7.2.75.1 Element: Feeder
|
Positions of alternate feeders including the feeder specified in Position on a feeding chain. Alternate feeders share the load according to the policy defined in FeederSynchronization . If not specified, it defaults to the value of Position . AlternatePositions must be non-negative. |
||
|
Specifies the synchronization of multiple Feeder Elements with identical Component Elements: Alternate - The feeders specified in Position alternate. Backup - This Feeder is the backup feeder for the Component in case of a misfeed or malfunction. The priority of backup feeders is defined by their position in AlternatePositions . Chain - This feeder is activated as soon as the feeder prior to it in the list is empty. Primary - This Feeder is the primary feeder for the Component . |
||
|
AddOn - Add on feeder, (e.g., CDs). BookBlock - A feeder for book blocks. New in JDF 1.4 Folding - A folding feeder that folds the input Component or Media . |
||
|
Bundle - Stream feeder, using the output of the Bundling Process. FanFold - Automatic loading of FanFold Media . Manual - Manual loading of stacks Online - Loaded by a gripper or conveyor. PrintRoll - Automatic loading of single products from a print Roll, using the output of the PrintRolling Process. |
||
|
Specifies the opening of Signatures: |
||
|
Position of feeder on a collecting and gathering chain in chain movement direction. Position = "0" is first feeder feeding to the collecting and gathering chain. Only one Feeder can be specified for any given Position . If Position is negative, it specifies the position counted from the back of the chain, (e.g., "-1" = last position, "-2" = next to last position, etc.). |
||
|
Specifies the Component that is to be loaded into this Feeder . This Component must be an input of the Feeding Process. Exactly one of Component or Media must be specified. |
||
|
Media ? |
Specifies the Media that is to be loaded into this Feeder . This Media must be an input of the Feeding Process. Exactly one of Component or Media must be specified. |
7.2.75.2 Element: FeederQualityParams
The FeederQualityParams Element defines the setup and policy for feeding quality control. It can be specified individually for each Feeder .
7.2.75.3 Element: CollatingItem
|
In case of nested bundles with BundleType = "Stack" , this parameter addresses the element to be consumed within the “tree” of such bundles. If the real bundle depth level ( BundleType = "Stack" ) is smaller than the value of BundleDepth , individual stack items (i.e., the smallest available level) shall be consumed. If the input component referenced does not contain bundles, then this parameter is ignored. A BundleDepth value of "0" means the Component itself. A value of "1" addresses the BundleItem Elements referenced from the Component , i.e. the Component / Bundle / BundleItem / Component (Ref), and so on |
||
|
Named Orientation of the CollatingItem relative to the input coordinate system. For details see Table 2-4, “Matrices and Orientation values for describing the orientation of a Component”. At most one of Orientation or Transformation must be specified. If neither is specified, no transformation is applied. The transformation specified here is applied in addition to orientation/transformation specified in the respective ResourceLink . |
||
|
Orientation of the Component respective to the input coordinate system. This Transformation specified here is applied in addition to orientation/transformation specified in the respective ResourceLink . At most one of Orientation and Transformation must be specified. If neither is specified, no transformation is applied. |
||
|
This parameter specifies the object, which is to be manipulated in orientation/transformation, and it is important to determine the sequence of stack items after flipping. StackItem - Apply individually to the smallest element on the stack which can be manipulated individually, (e.g., to a single Sheet in the case of a stack of Sheets). Component - Apply to each single element of a CollatingItem individually. CollateItem - apply to a CollatingItem as a whole. Note: If Amount = "1" , Component and CollatingItem are referring to the same object and, therefore, result in the same output. |
||
|
References one of the input components to the Process to be (partially) consumed by the CollatingItem Element. This Component must be an input of the Feeding Process. Exactly one of Component or Media must be specified. |
||
|
Media ? |
References one of the input media to the Process to be consumed by the CollatingItem Element. This Media must be an input of the Feeding Process. Exactly one of Component or Media must be specified. |
Note: Most real world Devices process stack items one by one, and hence will hardly ever support TransformationContext = "CollateItem" . This requires some kind of buffer for the stack items belonging to a single collating item plus a flipping mechanism for PrintRolling Process.
7.2.76 FileSpec
Specification of a file or a set of files. If a single FileSpec instance specifies a set of files, it must do so using the FileFormat and FileTemplate Attributes to specify a sequence of URLs. Otherwise, each FileSpec instance specifies a single file. If that single file is inside a container file (e.g., a Zip file or is compressed or encoded as indicated by Compression ), the FileSpec instance must define a Container Subelement which defines another FileSpec instance that specifies the container file. In such a case, the Attributes of each FileSpec instance must apply only to the properties of the file at that level.
ApprovalSuccess / ApprovalDetails , AssetListCreationParams , ByteMap , Color , Color / PrintConditionColor , ColorCorrectionParams , ColorCorrectionParams / ColorCorrectionOp , ColorSpaceConversionOp , ColorSpaceConversionParams , DBMergeParams , Device / IconList / Icon , DieLayout , ElementColorParams , ExposedMedia , ExternalImpositionTemplate , FileSpec / Container , FileSpec / FileAlias , FormatConversionParams / TIFFFormatParams / TIFFEmbeddedFile , ImageReplacementParams , LayoutElement , PDLResourceAlias , PrintCondition , QualityControlResult , ScanParams , ShapeDef , ShapeDefProductionParams / ObjectModel , ShapeDefProductionParams / ShapeTemplate
|
Creator application. See AppVersion for the application version number. |
||
|
Operating system of the application that created the file. Note: Additional values can be used from the IANA Operating System Names [iana-os] which allows up to 40 uppercase US ASCII alphabetical values as well as “-”, “_” and “/” -- but only for values not covered by the above values. For example, “OS/2” . See Appendix S, “AppOS and OSVersion Attributes” for combinations of AppOS and OSVersion values. |
||
|
Checksum of the file being referenced using the RSA MD5 algorithm. In JDF 1.1A, the term RSA MD was completed to RSA MD5. The data type was modified to hexBinary to accommodate the 128 bit output of the MD5 algorithm. The CheckSum must be for the entire file, not just parts of the file. |
||
|
Indicates the compression or encoding for the entire file. This is not compression used internally within the file. Base64 - A format for encoding arbitrary binary information for transmission by electronic mail. [RFC3548] BinHex - BinHex encoding converts an 8-bit file into a 7-bit format, similar to Uuencoding [RFC1741] . Compress - UNIX compression [RFC1977] . Deflate - The file is compressed using Zip public domain compression format [RFC1951] . Gzip - GNU Zip compression technology [RFC1952] . MacBinary - A format that combines the two forks of a Mac file, together with the file information into a single binary data stream, suitable for storage or transferring through non-Mac systems. [macbinary] None - The file is neither compressed nor encoded. UUEncode - A set of algorithms for converting files into a series of 7-bit ASCII characters that can be transmitted over the Internet. [uuencode] ZLIB - ZLIB compression [RFC1950] . |
||
|
Indicates what the Device is to do with the file when the Process that uses this Resource as an Input Resource completes. Unlink - The Device is to release the file. Delete - The Device is to attempt to delete the file. Retain - The Device is to do nothing with the file. Deprecation note: starting with JDF 1.2, retention of assets is specified in the Disposition Resource. |
||
|
The natural language of the document this FileSpec refers to. If the document contains more than one language, the value is the primary language of the document. |
||
|
Encoding or code page of the file contents.
Values include those from:
|
||
|
A formatting string used with the FileTemplate Attribute to define a sequence of URLs in a batch Process, each of which has the same semantics as the URL Attribute. Values are from: Appendix I, “Generating strings with Format and Template” . Constraint: if neither URL nor UID is present, both FileFormat and FileTemplate must be present, unless the Resource is a pipe. If either URL or UID is specified, then FileFormat and FileTemplate must not be specified. |
||
|
Size of the file in bytes. The data type was changed from integer to LongInteger in JDF 1.2. |
||
|
Identifies the model of the JDF Device for which the document was formatted, including manufacturer name, when the file is Device-dependent. Default behavior: the file is Device independent Value format is from: IEEE 1284-2000 Device ID string. Note: the value of this Attribute must exactly match the IEEE 1284-2000 Device ID string, except the length field must not be specified. See the Microsoft Universal Plug-and-Play [UPNP] section 2.2.6 DeviceId parameter for details. Example: it shows only the required fields for a PostScript document formatted for a LaserBeam 9 : MANUFACTURER:ACME Co.;COMMAND SET:PS;MODEL:LaserBeam 9; (See [IEEE1284] clause 7.6) |
||
|
A template, used with FileFormat , to define a sequence of URLs in a batch Process, each of which has the same semantics as the URL Attribute. Constraint: if neither URL nor UID is present, both FileFormat and FileTemplate must be present, unless the Resource is a pipe. Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
Version of the file referenced by this FileSpec . |
||
|
MIME type or file type of the file (or files of identical type when specifying a sequence of file names using the FileFormat and FileTemplate Attributes). See Compression for the indication of compression or encoding of the file. See MimeTypeVersion for the format version. If the file format has a MIME Media Type [iana-mt] registered with IANA, that value must be used. The [RFC2046] defines that MIME Media Types are case-insensitive. If the file format does not have a MIME Media Type registered with IANA, then the JDF spec defines string values, called file types, which must be used. Values include those from: Appendix H, “MimeType and MimeTypeVersion Attributes” . |
||
|
The level or version of the file format identified by MimeType , whether the value of MimeType is a MIME Media Type or a file type value defined by the JDF spec. Example values include:
"PDF/1.3"
,
"PDF/1.4"
and
"PDF/X-1a:2001"
"TIFF-IT/FP:1998"
,
"TIFF-IT/CT:1998"
and Values include those from: Appendix H, “MimeType and MimeTypeVersion Attributes” . |
||
|
Version of the operating system specified by AppOS . The IANA Registry provides a list. Values include those from: Table S-1, “AppOS and OSVersion Examples” . |
||
|
Policy that specifies the policy to follow when a file already exists and the FileSpec is used as an Output Resource. Overwrite - Overwrite the old file. RenameNew - Rename the new file. RenameOld - Rename the old file. NewVersion - Create a new file version. Only valid when the FileSpec references a file on a version aware file system. |
||
|
Indicates the order of pages in the file containing pages. Ascending - The first page in the file is the lowest numbered page. Descending - The first page in the file is the highest numbered page. |
||
|
Password or decryption key that is needed to read the file contents. Note: since this password string is not encrypted, it should only be passed around within a protected environment. |
||
|
RequestQuality specifies a requested quality of the encoded data when reading image data with selected MimeType values which support variable quality. RequestQuality is ignored when the FileSpec is referenced from an Output Resource or the FileSpec does not reference image data which support variable quality. The value in the range of 0 to 1.0 represents a factor of the maximum quality encoded in the file. If left unspecified, the value defaults to 1.0 meaning all information encoded will be returned. The following details how values are interpreted for the supported MimeType values: image/ jp2 , image/jpx - The value represents the ratio of the encoding bitrate of the maximum bitrate layer encoded in the file. image/gif - (Note: Only interleaved GIF) The number represents a ratio of the total interleaved layers of the file. image/tiff - (Note: Only pyramid TIFF) The number represents the ratio of the total resolution of the complete image. |
||
|
If an Element uses more than one FileSpec Subelement, this Attribute is used to refer from the parent Element to a certain child Element of this type, for example, see FormatConversionParams . Values include those from: Table 7-184, “ResourceUsage Attribute Values”. |
||
|
Used when ResourceUsage = "SearchPath" to specify the maximum directory depth that will be recursively searched. 0 specifies this directory only, "INF" specifies an unlimited search. |
||
|
Unique internal ID of the referenced file. This Attribute is dependent on the type of file that is referenced: PDF - Variable unique identifier in the ID field of the PDF file’s trailer. ICC Profile - The Profile ID in bytes 84-99 of the ICC profile header. Constraint: If neither URL nor UID is present on an input FileSpec , and neither FileFormat nor FileTemplate is present, the referencing Resource must be a pipe. If either URL or UID is specified, then FileFormat and FileTemplate must not be specified. |
||
|
Location of the file specified as either an Absolute URI or a Relative URI. If neither URL nor UID is present on an input FileSpec , and neither FileFormat nor FileTemplate is present, the referencing Resource must be a pipe. If either URL or UID is specified, then FileFormat and FileTemplate must not be specified. If URL is not specified in an Output Resource, the system-specified location will be assumed, but this value must be updated as soon as the Output Resource is available. For example, an instruction for a digital delivery JDF Device to compress the files may specify the output RunList with the Compression Attribute without the URL Attribute. See [RFC3986] and Appendix J, “Resolving RunList/@Directory and FileSpec/@URL URI References” and Appendix M, “FileSpec Attributes and Container Subelement” for the syntax and examples. For the "file" URL scheme see also [RFC1738] and [FileURL] . |
||
|
A user-friendly name which can be used to identify the file. May be used by an agent to identify a file on a Device without knowing its internal location. |
||
|
Specifies the container for this file. When a container FileSpec is pointed to by Container , that FileSpec must not also specify FileFormat and FileTemplate Attributes. The container mechanism may be used recursively, (e.g., for a Zip file held in a tar file, a Zip file in a Zip file, an encoded Zip file, etc.). See Appendix J, “Resolving RunList/@Directory and FileSpec/@URL URI References” for details. |
||
|
Indicates what the Device should do with the file when the Process that uses this Resource completes. If not specified here or in the parent RunList , the file specified by this FileSpec should not be deleted by the Device. If FileSpec / Disposition is specified, it takes precedence over RunList / Disposition . |
||
|
Defines a set of mappings between file names that can occur in the document and URLs (which can refer to external files or parts of a MIME message). |
-- Attribute: ResourceUsage
|
Used for ColorCorrectionOp / FileSpec and ColorSpaceConversionOp / FileSpec |
|
|
Used for ElementColorParams / FileSpec |
|
|
Used for ScanParams / FileSpec |
|
|
Used for ColorCorrectionOp / FileSpec |
|
|
Used for ColorCorrectionParams / FileSpec and ColorSpaceConversionParams / FileSpec |
|
|
Used for FormatConversionParams / FileSpec |
|
|
Used for FormatConversionParams / FileSpec |
|
|
Used for ExposedMedia / FileSpec |
|
|
Used for ElementColorParams / FileSpec |
|
|
Used for ScanParams / FileSpec |
|
|
Used for AssetListCreationParams / FileSpec and ImageReplacementParams / FileSpec |
|
|
Used for ColorSpaceConversionOp / FileSpec |
|
|
Used for PrintCondition / FileSpec , ScanParams / FileSpec , Color / FileSpec and PrintConditionColor / FileSpec |
|
|
Used for ColorCorrectionParams / FileSpec and ColorSpaceConversionParams / FileSpec |
7.2.76.1 Element: Container
The Container specifies the containing file for a FileSpec , e.g., a zip file or tar archive. The Container Elements may be specified recursively in their respective child FileSpec Elements.
|
Link to another FileSpec Resource that describes the container, (e.g., a packaging file, such as Zip, Multipart/Related, tar file or an otherwise compressed or encoded file that contains the file represented by this FileSpec Resource). The link value is only to be used for locating that container FileSpec Resource. See Appendix J, “Resolving RunList/@Directory and FileSpec/@URL URI References” for details. |
7.2.76.2 Element: FileAlias
|
Indicates what the Device is to do with the file referenced by this alias when the Process that uses this Resource as an Input Resource completes. Unlink - The Device is to release the file. Delete - The Device is to attempt to delete the file. Retain - The Device is to do nothing with the file. Deprecation note: starting with JDF 1.2, use FileSpec / Disposition . |
||
|
Deprecation note: starting with JDF/1.2, use FileSpec /@ MimeType . |
||
|
Representation of the original 8-bit byte stream of the Alias Name. Used to transport the original byte representation of an Alias name when moving JDF tickets between computers with different locales. |
||
|
The URL which identifies the file the alias refers to. In JDF/1.2 and beyond, use FileSpec /@ URL . |
||
|
FileSpec ? |
For JDF version 1.2 and beyond, FileSpec must be present, and must contain a URL Attribute. FileSpec may contain additional properties of the file, (e.g., Disposition , MimeType , MimeTypeVersion , etc.). |
7.2.77 FitPolicy
This Resource specifies how to fit content into a receiving container e.g., a RunList entry into a PlacedObject or content into either a PageCell or a PageCell grid in a SurfaceContentsBox . See the description of each reference to FitPolicy to determine what the context-specific “content” is and what the “receiving container” is.
ImageSetterParams , InterpretingParams , Layout / PlacedObject , LayoutPreparationParams , LayoutPreparationParams / PageCell , RasterReadingParams
|
Defines the offset (position) of the imaged area in the non-rotated source image when SizePolicy is "ClipToMaxPage" . The values 0.0 0.0 mean that the imaged area starts at the lower left point of the receiving container. If absent, the imaged area is taken from the center of the source image. If FitPolicy is defined in the context of a PageCell , ClipOffset is ignored when PageCell /@ ImageShift is specified. |
||
|
Allows printing of NUp grids even if the media size does not match the requirements of the data. GutterPolicy MUST NOT be specified when FitPolicy is referenced from a Layout Resource. Distribute - The gutters can grow or shrink to the value specified in MinGutter . |
||
|
Minimum width in points of the horizontal and vertical gutters formed between rows and columns of pages of a multi-up Sheet layout. The first value specifies the minimum width of all horizontal gutters and the second value specifies the minimum width of all vertical gutters. MinGutter MUST NOT be specified when FitPolicy is referenced from a Layout resource. |
||
|
Specifies the policy for the Device to automatically rotate the content to optimize the fit of the content to the receiving container. RotateOrthogonal - Rotate by 90˚ in either direction. |
||
|
Allows printing even if the container size does not match the requirements of the data. ClipToMaxPage - The page contents are to be clipped to the size of the container. The printed area is either centered in the source image if no ClipOffset key is given, or from that position which is determined by ClipOffset . Abort - Emit an error and abort printing. FitToPage - The page contents are to be scaled up or down to fit the container. The aspect ratio is maintained. ReduceToFit - The page contents are to be scaled down but not scaled up to fit the container. The aspect ratio is maintained. Tile - the page contents are to be split into several tiles, each printed on its own surface. |
7.2.78 Fold
Fold describes an individual folding operation of the Component .
FoldingIntent , BinderySignature , FoldingParams
|
Direction in which it is folded. Up - Upwards; corresponds to a valley fold with the left/bottom side coming over the opposite side. Down - Downwards; corresponds to a mountain or peak fold with the left/bottom side coming under the opposite side. |
||
|
Distance of the reference edge relative to From . If both Travel and RelativeTravel are specified, RelativeTravel is ignored. At least one of Travel or RelativeTravel must be specified. |
||
|
Relative distance of the reference edge relative to From in the coordinates of the incoming Component . The RelativeTravel is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0, which specifies the full length of the input Component . At least one of Travel or RelativeTravel must be specified. |
7.2.79 FoldingParams
This Resource describes the folding parameters, including the sequence of folding steps. It is also possible to execute the predefined steps of the folding catalog. After each folding step of a folding procedure, the origin of the coordinate system is moved to the lower left corner of the intermediate folding product. For details see Section 2.5.4, “Product Example: Simple Brochure” .
The specification of reference edges (i.e., Front , Rear , Left and Right ) for the description of an operation (e.g., the positioning of a tool) is done by means of determined names as shown in Figure 7-32, below.
BlockName , RibbonName , SheetName , SignatureName , WebName
|
How the folding operations are described. FoldProc - Detailed description of each individual fold. FoldCatalog - Selection of fold procedure from FoldCatalog . Deprecation note: starting with JDF 1.2, the FoldCatalog defines the topology of the folding scheme. The specifics of each individual fold can be described using Fold Elements. If both FoldCatalog and Fold are specified, Fold takes precedence |
||
|
Describes the type of fold according to the folding catalog in Figure 7-33, “Fold catalog part 1” and Figure 7-34, “Fold catalog part 2”. In case of any ambiguity, the folding notation takes precedence over the graphic illustration in the aforementioned Figures. Value format is: " Fn-i " where “n” is the number of finished pages and “i” is either an integer, which identifies a particular fold or the letter "X" , which identifies a generic fold. E.g., "F6-2" describes a Z-fold of 6 finished pages, and "F6-X . " describes a generic fold with 6 finished pages. Modification note: starting with JDF 1.4, the letter "X" is added for a generic fold |
||
|
Input Sheet format. If the specified size does not match the size of the X and Y dimensions of the input Component , all coordinates of the folding procedure are scaled accordingly. The scaling factors in X and Y direction may differ. Implementation Note: This Attribute should always match the Size Attribute of the input Component , which is the default. |
||
|
Note: SheetLay does not modify the coordinate references of the Folding Process. |
||
|
Fold * |
Describes the folding operations in the sequence in which they are to be carried out. It is recommended to specify a set of subsequent Fold operations as multiple Fold Elements in one Folding procedure, rather than specifying a Combined Process that combines multiple Folding Processes. If both FoldCatalog and Fold Elements are specified, the Fold Elements have precedence, and the FoldCatalog specifies only the topology. For instance a cover-fold with a page size ratio of 0.52 to 0.48 would still be defined as an " F4-1 " . |
|
|
Abstract Element that describes the folding operations in the sequence in which they are to be carried out. Replaced by the explicit Fold Element in JDF 1.1 and beyond. |
|
|
7.2.80 FontParams
This Resource describes how fonts are handled when converting PostScript or other PDL files to PDF.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
7.2.81 FontPolicy
This Resource defines the policies that Devices follow when font errors occur while PDL files are being processed. When fonts are referenced by PDL files but are not provided, Devices must provide one of the following two fallback behaviors:
- 1 The Device provides a standard default font which is substituted whenever a font cannot be found.
- 2 The Device provides an emulation of the missing font.
If neither fallback behavior is requested (i.e., both UseDefaultFont and UseFontEmulation are "false" ), then the Job will fail if a referenced font is not provided. The FontPolicy allows Jobs to specify whether either of these fallback behaviors are to be employed when missing fonts occur.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
7.2.82 FormatConversionParams
This Resource defines the parameters needed for generic FormatConversion of digital files.
|
FileSpec ( InputFormat ) ? |
The format of the original file is specified in a FileSpec with ResourceUsage = "InputFormat" . A URL should not be specified because the list of files is given by the input RunList of the FormatConversion Process. The purpose of this Element in JDF 1.1 and earlier was to provide the MIME type of the file to be created. This is now defined directly using the FileSpec of the input RunList of the FormatConversion Process. |
|
|
FileSpec ( OutputFormat ) ? |
The format of the converted file is specified in a FileSpec with ResourceUsage = "OutputFormat" . A URL should not be specified because the list of files is given by the output RunList of the FormatConversion Process. The purpose of this Element in JDF 1.1 and earlier was to provide the MIME type of the file to be created. This is now defined directly using the FileSpec of the output RunList . |
|
|
Parameters specific to conversion of rasters to TIFF files. (See below.) FormatConversion should not be used to convert non-raster files to TIFF. The appropriate Interpreting and Rendering Processes should be used first. |
||
|
Provides a set of controls that determines how images will be down-sampled and compressed in the converted documents |
||
|
Additional detail about the colors used in the file to be converted. |
To control the creation of files in formats other than TIFF, equivalent Subelements to TIFFFormatParams may be defined. It is possible to use ImageCompressionParams to request de-screening of 1-bit per channel rasters to contone rasters (usually accompanied by a reduction in resolution). Additional data regarding the screens used in the original rasters may be provided as a ScreeningParams Resource supplied in a LayoutElement as part of the input RunList .
7.2.82.1 Element: TIFFFormatParams
|
Note: the identifier values have been selected to match the identifier with the same purpose within the TIFF file itself. |
||
|
How the components of each pixel are stored. The values are taken from TIFF tag 284-- PlanarConfiguration : |
||
|
When writing monochrome or grayscale files, this flag indicates whether the data is to be written as “WhiteIsZero” or “BlackIsZero.” |
||
|
How the image data are segmented. SingleStrip - all data are included in one segment. This is encoded in the TIFF file by setting RowsPerStrip to a number equal to or larger than the number of pixel rows in the image. |
||
|
The number of image scan lines per strip, encoded in the TIFF file as RowsPerStrip. This Attribute is ignored if Segmentation ! = "Stripped" . The default, when not known, is set by the processing system with the exception that when converting from ByteMap to TIFF, ByteMap /@ BandHeight is the default. |
||
|
Two integers. The X value provides width of tiles, and the Y value provides height of tiles. This Attribute is ignored if Segmentation is not "Tiled" . |
||
|
When color separations are stored in individual TIFF files it is often useful to mark each with the name of the colorant that it represents, but there is no universally accepted way to do this. In order to avoid the need for explicit Partitioning, the tag to be used to encode the separation name (as a string) can be entered here as the TIFF tag number. If the same TIFF tag number is also supplied as a TIFFtag Subelement, then the TIFFtag Element takes priority over SeparationNameTag . The tag should only be put in the resulting TIFF files if the name of the separation is known, (e.g., from a ColorPool Resource supplied to FormatConversion , or because the FormatConversion Process forms a part of a compound process with a Separation Process). The default of "270" is the TIFF ImageDescription tag. |
||
|
TIFFtag * |
||
|
Files to be embedded within the created TIFF file. These might include an ICC profile, XMP data, etc. |
The number of channels should be derived from the raster data to be converted.
When the PhotometricInterpretation tag = 5 and the InkSet tag = 2, it is strongly recommended that the NumberOfInks and InkNames tags be completed--separation names may be obtained from the ColorPool Resource supplied to FormatConversion .
Flate and JPEG compression in resulting TIFF files should use Compression = 8 and Compression = 7 respectively, as documented in [TIFFPS] . In particular, the JPEG encoding using Compression = 6, as described in [TIFF6] should not be used.
7.2.82.2 Element: TIFFtag
|
If the type of the tag is UNDEFINED, then BinaryValue is used to encode the data |
||
|
If the type of the tag is BYTE, SHORT, LONG, SBYTE, SSHORT or SLONG, then IntegerValue is used to encode that data |
||
|
If the type of the tag is RATIONAL, SRATIONAL, FLOAT or DOUBLE, then NumberValue is used to encode that data |
||
|
If the type of the tag is ASCII, then StringValue is used to encode the data. |
||
|
Tag number of the specified tag, (e.g., 270 (decimal) for ImageDescription). |
||
|
The type of the tag as defined in [TIFF6] (1 = BYTE, 2 = SHORT, etc.) |
Exactly one of IntegerValue , NumberValue , StringValue or BinaryValue must be present, depending on the type of the TIFF tag to be carried. TIFFtag Elements must not be used for any tags related to the image data and its encoding (ImageWidth, Compression, etc.). TIFFtag Elements may include informational tags such as OPIProxy, ImageID, Copyright, DateTime, ImageDescription, etc.
7.2.82.3 Element: TIFFEmbeddedFile
|
Tag number of the specified tag, (e.g., 34675 (decimal) for an ICC profile or 700 for XMP). |
||
|
The type of the tag as defined in [TIFF6] . This will usually be 1 (BYTE) or 7 (UNDEFINED). |
||
7.2.83 GatheringParams
This Resource contains the Attributes of the Gathering Process.
|
7.2.84 GeneralID
Modification note: starting with JDF 1.4, GeneralID becomes an Element, and is no longer a Resource. See Section 3.1.2, “GeneralID”. GeneralID becomes a child of any Element. See Table 3-1, “Any Element (generic content)”. The remainder of this section has the text that was present in JDF 1.3, except that the table has been moved to Section 3.1.2, “GeneralID”.
GeneralID describes a generic identifier. The name or usage of the identifier is specified in GeneralID /@ IDUsage and the specific value of the identifier is specified in GeneralID /@ IDValue .
7.2.85 GlueApplication
This Resource specifies glue application in hard and soft cover book production.
CasingInParams , CoverApplicationParams , GluingParams / Glue , SpineTapingParams
|
7.2.86 GlueLine
This Resource provides the information to determine where and how to apply glue.
Insert , BoxFoldingParams , BoxFoldAction , CaseMakingParams , CoverApplicationParams , EndSheetGluingParams / EndSheet , FoldingParams , GluingParams / Glue , HeadBandApplicationParams , InsertingParams , Media / MediaLayers , SpineTapingParams , ThreadSealingParams , ThreadSewingParams
|
Specifies that this GlueLine is to cover the complete width of the Component it is applied to. |
||
|
Width of the glue line. Note that in extreme cases, the glue line could cover the input component over the whole width. |
||
|
ColdGlue - Any type of glue that needs no heat treatment. |
||
|
Glue line pattern defined by the length of a glue line segment (1st Element, 3rd and all odd elements of the NumberList) and glue line gap (2nd Element, 4th and all even elements of the NumberList). A solid line is expressed by the pattern (1 0). GluingPattern must contain an even number of entries. If the total length of GluingPattern is less than WorkingPath or the length implied by RelativeWorkingPath , the pattern restarts after the last gap. If the total length of GluingPattern is larger than WorkingPath or the length implied by RelativeWorkingPath , the pattern is clipped at the end. |
||
|
Temperature needed for melting the glue, in degrees centigrade. |
||
|
Relative starting position of the tool. The RelativeStartPosition is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0 for each component of the XYPair, which specifies the full size of the input Component . |
||
|
Relative working path of the tool beginning at RelativeStartPosition . The RelativeWorkingPath is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0 for each component of the XYPair, which specifies the full size of the input Component . |
||
|
Start position of glue line. The start position is given in the coordinate system of the mother Sheet. If both StartPosition and RelativeStartPosition are specified, RelativeStartPosition is ignored. |
||
|
Relative working path of the gluing tool. If both WorkingPath and RelativeWorkingPath are specified, RelativeWorkingPath is ignored. |
7.2.87 GluingParams
GluingParams define the parameters applying a generic line of glue to a component.
ProductionRun , WebName , WebProduct
|
Glue * |
Definition of one or more Glue line applications. |
7.2.87.1 Element: Glue
The Glue Element describes how to apply a line of glue.
|
Describes the glue application. Exactly one of GlueApplication or GlueLine must be specified. |
||
|
GlueLine ? |
Structure of the GlueLine used for generic gluing. Exactly one of GlueApplication or GlueLine must be specified. |
7.2.88 HeadBandApplicationParams
This Resource specifies how to apply headbands in hard cover book production.
|
Bottom head band brand. If not specified, defaults to the value of TopBrand . |
||
|
Color of the bottom head band. If not specified, defaults to the value of TopColor . |
||
|
A more specific, specialized or site-defined name for the color. If BottomColorDetails is supplied, BottomColor SHOULD also be supplied. |
||
|
Length of the carrier material of the bottom head band along binding edge. If not specified, both head bands are on one carrier. |
||
|
A more specific, specialized or site-defined name for the color. If TopColorDetails is supplied, TopColor SHOULD also be supplied. |
||
|
Length of carrier material of the top head band along binding edge. If not specified, both head bands are on one carrier which has the length of the book block. |
||
|
GlueLine * |
The carrier can be applied to the book block with glue. The coordinate system for the GlueLine is defined in the Section 7.2.72, “EndSheetGluingParams”. |
7.2.89 Hole
The Hole Resource describes an individual hole.
HoleLine , HoleList , HoleMakingParams
|
Position of the center of the hole relative to the Component coordinate system. For more information, see Section 6.7.2, “HoleMaking”. |
||
|
Size (Bounding Box) of the hole, in points. If Shape is "Round" , only the first entry of Extent is evaluated and defines the hole diameter. |
||
7.2.90 HoleLine
Line hole punching generates a series of holes with identical distance (pitch) running parallel to the edge of a Web, which is mainly used to transport paper through continuous-feed printers and finishing Devices (form processing). The final product typically is a Web with two lines of holes, one at each edge of the Web. The parameters for one line of holes are specified in the HoleLine Resource. The distance between holes within each line of holes is identical (constant pitch).
|
Size and position of the first hole in the HoleLine . |
|
However, sometimes Line Hole Punching is performed for multiple webs before dividing the Web after the HoleMaking Process as illustrated in Figure 7-38 below:
|
7.2.91 HoleList
This Resource is used to describe holes or rows of holes in Intent Resource s or Media . Note that it was an Intent Resource Subelement prior to JDF 1.2.
BindingIntent / CoilBinding , BindingIntent / PlasticCombBinding , BindingIntent / StripBinding , BindingIntent / WireCombBinding , BindingIntent / BindList / BindItem / CoilBinding , BindingIntent / BindList / BindItem / PlasticCombBinding , BindingIntent / BindList / BindItem / StripBinding , BindingIntent / BindList / BindItem / WireCombBinding , HoleMakingIntent , Media
|
Hole * |
Description of individual holes. See Section 7.2.89, “Hole”. |
|
|
HoleLine * |
Array of all HoleLine Elements. See Section 7.2.90, “HoleLine”. |
7.2.92 HoleMakingParams
This Resource specifies where to make a hole of what shape in components. This information is used by the HoleMaking Process.
Default behavior for HoleCount: For dealing with the Default case of HoleCount (i.e. when not supplied), intelligent systems will take into consideration Job parameters like the length of the binding edge or distance of holes to the paper edges to calculate the appropriate number of holes. For production of the holes and selection/production of the matching binding Element, the “system specified” values need to match 100% between the HoleMaking and the binding Process for obvious reasons. In practice, if no details are specified for HoleMaking , they should also be absent for binding. In this case, either the operator provides the missing value when setting up the binding Device for the Job, or the Device itself needs to have some kind of automatic hole detection mechanism.
CoilBindingParams , PlasticCombBindingParams , RingBindingParams , StripBindingParams , WireCombBindingParams
|
Position of the center of the hole pattern relative to the Component coordinate system if HoleType is not "Explicit" . If not specified, it defaults to the value implied by HoleType . |
||
|
Defines the reference coordinate system for Center . TrailingEdge - Physical coordinate system of the component. RegistrationMark - The center is relative to a registration mark. |
||
|
Size (Bounding Box) of the hole in points if HoleType is not "Explicit" . If Shape is "Round" , only the first entry of Extent is evaluated and defines the hole diameter. If not specified, it defaults to the value implied by HoleType . |
||
|
For patterns with HoleType whose enumeration values begin with a "P" , "W" or "C" , this parameter specifies the number of consecutive holes and spaces. The first entry defines the number of holes, the second entry defines the number of spaces, and consecutive entries alternately define holes ( h ) and spaces (s), for instance: |
||
|
The edge of the media relative to where the holes are to be punched. Use with HoleType. Default value: if HoleType is "Explicit" , "Pattern" ; otherwise "Left" . Pattern - Specifies that the reference edge implied by the value of HoleType in Appendix L, “JDF/CIP4 Hole Pattern Catalog” is used. Deprecation note: starting with JDF 1.1, use an explicit Transformation or Orientation of the input Component . If either Transformation or Orientation along with HoleReferenceEdge is specified, the result is the matrix product of both transformations. Transformation or Orientation must be applied first. |
||
|
Predefined hole pattern. Multiple hole patterns are specified as one NMTOKENS string, (e.g., 3-hole ring binding and 4-hole ring binding holes on one piece of media). Explicit - Holes are defined in an array of Hole Elements. 2HoleEuro - Replaced by either R2m-DIN or R2m-ISO . Deprecated in JDF 1.0 3HoleUS - Replaced by R3I-US . Deprecated in JDF 1.0 4HoleEuro - Replaced by either R4m-DIN-A4 or R4m-DIN-A5 . Deprecated in JDF 1.0 Values are from: Appendix L, “JDF/CIP4 Hole Pattern Catalog” . |
||
|
Shape of the holes if HoleType is not "Explicit" . |
||
|
Hole * |
Description of individual Hole Elements. |
|
|
HoleLine * |
Description of HoleLine Elements. |
|
|
Reference to the registration mark that defines the coordinate system origin for HoleMaking . |
7.2.93 IdentificationField
This Resource contains information about a mark on a document (e.g., a bar code) used for OCR-based verification purposes or document separation.
Abstract Physical Resource , Disjointing , EmbossingParams / Emboss , Layout / MarkObject , LayoutElementProductionParams / LayoutElementPart / BarcodeProductionParams
|
Box that provides the boundaries of the mark that indicates where the IdentificationField is placed. If the IdentificationField is specified in a Layout , the coordinate system is defined by the MarkObject containing the IdentificationField . If no Layout context is available, the origin of the coordinate system is defined as the lower left corner of the Resource surface that Position specifies when the specified surface is viewed in its natural orientation. Each item in the list below specifies a value of Position and the corner that is the origin for the specified value when the viewer is positioned in front of the front surface. For example, when Position = "Left" , the origin is the bottom-back corner of left surface when viewed from the front surface of the Resource and lower-left corner when viewed from the left surface.
If no BoundingBox is defined and the IdentificationField is specified
The BoundingBox is used only as metadata when searching or scanning IdentificationField Elements and not used when generating IdentificationField Elements in a LayoutElementProduction Process. |
|||
|
Barcode - Any bar code. New in JDF 1.3 BarCode1D - One-dimensional bar code. Deprecated in JDF 1.3 BarCode2D - Two-dimensional bar code. Deprecated in JDF 1.3 |
|||
|
Details about the encoding type. An example is the bar code scheme. Values include those from: Table 7-207, “EncodingDetails Attribute Values” . |
|||
|
Regular expression that defines the expected format of the expression, (e.g., the number of digits, alphanumeric or numeric). Note that this field may also be used to define constant fields, (e.g., the end of document markers or packaging labels). If not specified, any expression is valid. Exactly one of Format , Value or the pair ValueFormat and ValueTemplate must be specified. |
|||
|
Orientation of the contents within the IdentificationField . The coordinate system is defined in the system of the Sheet or component where the IdentificationField resides. The Orientation is used only as metadata when searching or scanning IdentificationField Elements and not used when generating IdentificationField Elements in a LayoutElementProduction Process. |
|||
|
Position with respect to the Instance Document or Physical Resource to which the Resource refers. Header - Sheet before the document. Trailer - Sheet after the document. Page - A page of the document. Top - The top of the Resource. Bottom - The bottom of the Resource. Left - The left side of the Resource. Right - The right side of the Resource. Front - The front side of the Resource. |
|||
|
If Position = "Page" , this refers to the page where the IdentificationField can be found. Negative values denote an offset relative to the last page in a stack of pages. |
|||
|
Purpose defines the usage of the field. Label - Used to mark a product or component. |
|||
|
More detail about the usage of the barcode. ProductIdentification - End product identification e.g., scanning in the super market. |
|||
|
Fixed value of the IdentificationField , (e.g., on a label). Exactly one of Format , Value or the pair ValueFormat and ValueTemplate must be specified. |
|||
|
A formatting string used with ValueTemplate to define fixed and/or variable content of barcodes or text. Values are from: Appendix I, “Generating strings with Format and Template” . Constraint: exactly one of Format , Value or the pair ValueFormat and ValueTemplate must be specified. |
|||
|
A list of values used with ValueTemplate to define fixed and/or variable content of barcodes or text. Values are from: Appendix I, “Generating strings with Format and Template” . Constraint: exactly one of Format , Value or the pair ValueFormat and ValueTemplate must be specified. |
|||
|
Additional values encoded in the IdentificationField . |
|||
-- Attribute: EncodingDetails
7.2.93.1 Element: BarcodeDetails
|
Values include those from: Table 7-211, “BarcodeVersion Values - for HIBC_DATAMATRIX”. Values include those from: Table 7-212, “BarcodeVersion Values - for QR barcodes”. |
||
|
Error correction level for barcodes having a separately definable error correction level. Each value can be used only for certain values of IdentificationField /@ EncodingDetails . PDF417_EC_0 - for EncodingDetails = PDF417 PDF417_EC_1 - for EncodingDetails = PDF417 PDF417_EC_2 - for EncodingDetails = PDF417 PDF417_EC_3 - for EncodingDetails = PDF417 PDF417_EC_4 - for EncodingDetails = PDF417 PDF417_EC_5 - for EncodingDetails = PDF417 PDF417_EC_6 - for EncodingDetails = PDF417 PDF417_EC_7 - for EncodingDetails = PDF417 PDF417_EC_8 - for EncodingDetails = PDF417 QR_EC_L - for EncodingDetails = QR QR_EC_M - for EncodingDetails = QR |
||
|
The number of cells in x direction of a matrix barcode. For DATAMATRIX this field can be omitted since BarcodeVersion already defines this. |
||
|
The number of cells in y direction of a matrix barcode For DATAMATRIX this field can be omitted since BarcodeVersion already defines this. |
7.2.93.2 Element: ExtraValues
|
Supplemental - UPC supplemental 2/5 digit symbology CompositeCode - This is applicable for barcodes like RSS -14 that have an optional composite code part. Coupon - The additional message for the EAN128 part of a UPC or EAN coupon. |
||
|
Additional value of the IdentificationField as specified in Usage . |
7.2.93.3 Usage of barcode Attributes
The following table specifies whether the Attributes Height , Magnification and Ratio are applicable for a given barcode type that is specified by EncodingDetails .
-- Attribute: BarcodeVersion - for HIBC_DATAMATRIX
The following table specifies valid values of BarcodeDetails /@ BarcodeVersion for a DATAMATRIX barcode:
Modification note: starting with JDF 1.3, these values are for "HIBC_DATAMATRIX" rather than "DATAMATRIX"
-- Attribute: BarcodeVersion - for QR barcodes
The following table specifies valid values of BarcodeDetails /@ BarcodeVersion for a QR barcode.
Example 7-22: Barcode
The following example illustrates the description of a barcode in a LayoutElementProduction Process:
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" DescriptiveName = "Barcode Creation"
ID = "n001" Status = "Waiting" JobPartID = "ID34" Type = "LayoutElementProduction"
< LayoutElementProductionParams Class = "Parameter" ID = "BarcodeParams"
< IdentificationField Encoding = "Barcode" EncodingDetails = "EAN_13"
Purpose = "Label" PurposeDetails = "ProductIdentification"
< BarcodeReproParams Height = "73.50" Magnification = "1.0" >
< BarcodeCompParams CompensationProcess = "Printing"
</ LayoutElementProductionParams >
< LayoutElement Class = "Parameter" ID = "LayElOut" Status = "Unavailable" />
< LayoutElementProductionParamsLink Usage = "Input" rRef = "BarcodeParams" />
< LayoutElementLink Usage = "Output" rRef = "LayElOut" />
7.2.94 IDPrintingParams
See Section P.4.6, “IDPrintingParams” for details of this deprecated Resource.
7.2.95 ImageCompressionParams
Prior to JDF 1.2 the filtering in ImageCompressionParams was based on the terminology in PostScript and PDF. Many image compression and decompression filters require additional information in the form of a filter parameter dictionary, and additional filter parameters have been added to meet this need.
ContentList / ContentData , FormatConversionParams , LayoutElement , PageList , PageList / PageData
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
ImageReplacement , PDLCreation , PSToPDFConversion ,
7.2.95.1 Element: ImageCompression
7.2.95.2 Element: CCITTFaxParams
7.2.95.3 Element: DCTParams
|
Identifies which of the incoming color spaces will be operated on. Values are from: Table 7-217, “SourceCSs Attribute Values”. Note: JDF 1.1 defined that CalRGB be treated as RGB, CalGray as Gray, and ICC-Based color spaces as one of Gray, RGB or CMYK depending on the number of channels. Note: In JDF 1.2, the data type was erroneously specified as enumeration, not enumerations. |
||
|
A sequence of horizontal sampling factors--one entry per color channel in the raster data. If not specified, the implied default is "1" for every channel. |
||
|
A sequence of vertical sampling factors--one entry per color channel in the raster data. If not specified, the implied default is "1" for every channel. |
||
|
Quantization tables. If present, there must be one QuantTable entry for each color channel. |
||
|
Huffman tables for DC and AC components. If present, there must be at least one HuffTable element for each color channel. |
||
|
Color transformation algorithm. None - Colors are not to be transformed. YUV - RGB raster values are to be transformed to YUV before encoding and from YUV to RGB after decoding. If four channels are present, transform CMYK values to YUVK before encoding and from YUVK to CMYK after decoding. Automatic - "YUV" for 3-channel raster data, "None" otherwise. |
When the DCTParams Element is a Subelement of ImageCompressionParams used in a FormatConversion Process to generate TIFF files, YUV is equivalent to YCbCr in TIFF terminology. The HSamples and VSamples values are used to set YCbCrSubSampling or CIELabSubSampling. This means that they are only relevant for data supplied as Lab, or data where ColorTransform is "YUV" ; that the first element must be 1 in each case; that the fourth element must be 1 where CMYK data is to be compressed; and that the second and third elements must equal each other.
-- Attribute: SourceCSs
|
Operates on CIE-Based color spaces (CIEBasedA, CIEBasedABC, CIEBasedDEF, CIEBasedDEFG). |
|
|
Identifies the source color encoding as a DeviceN color space. The specific DeviceN color space to operate on is defined in the DeviceNSpace Resource. If this value is specified then DeviceNSpace and ColorPool must also be present. |
|
|
Operates on Device independent color spaces (equivalent to Calibrated or CIE-Based or ICC-Based or Lab or YUV). |
|
|
Operates on color spaces defined using ICC profiles. ICC-Based includes EPS, TIFF or PICT files with embedded ICC profiles. See [ICC.1] . If IgnoreEmbeddedICC is "true" , then nominally ICC-Based files or elements is to be treated as being encoded in the alternate or underlying color space, and a ColorSpaceConversionOp where SourceCS = "DevIndep" is not to be applied, unless that color space is also Device independent. |
|
|
Operates on Separation color spaces (spot colors). The specific separation(s) to operate on are defined in the SeparationSpec Resource(s). If no SeparationSpec is defined, the operation will operate on all the separation color spaces in the input RunList . |
|
|
Operates on YUV (Also known as YCbCr). See [CCIR601-2] . |
7.2.95.4 Element: FlateParams
7.2.95.5 Element: JBIG2Params
|
If "true" requires JBIG2 compressed images to retain the exact representation of the original image without loss. |
7.2.95.6 Element: JPEG2000Params
7.2.95.7 Element: LZWParams
|
A code indicating when to increase the code word length. The TIFF specification can be interpreted to imply that code word length increases are postponed as long as possible. However, some existing implementations of LZW increase the code word length one code word earlier than necessary. The PostScript language supports both interpretations. If EarlyChange is "0" , code word length increases are postponed as long as possible. If it is "1" , they occur one code word early. Note: The default should not be used when this LZWParams Element is in ImageCompressionParams used as an Input Resource to a FormatConversion Process that is creating TIFF files. |
||
|
A code that selects the predictor function: 1 - No predictor (normal encoding or decoding). 10 - PNG predictor, None function. 11 - PNG predictor, Sub function. 12 - PNG predictor, Up function. 13 - PNG predictor, Average function. 14 - PNG predictor, Path function. 15 - PNG predictor in which the encoding filter automatically chooses the optimum function separately for each row. Note: On 1X PNG predictors, these values select the specific PNG predictor function(s) to be used, as indicated above. When decoding, the predictor function is explicitly encoded in the incoming data. |
7.2.96 ImageReplacementParams
This Resource specifies parameters to control image replacement within production workflows.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
|
Specifies the image pre-scanning strategy to be used on the input document data before starting the RIPing Process. NoPreScan - Do not pre-scan the document looking for references to images. PreScan - Pre-scan the document looking for references to images and making sure the data are accessible now so that the RIP will not encounter a fault later. PreScanAndGather - Pre-scan the document looking for references to images, and copy the data to a temporary place so that the RIP will be able to access the data with a predictable and small well-bounded delay later. |
||
|
Identifies how externally referenced images will be handled within the associated Process. Omit - Complete Process maintaining only references to external data. Proxy - Complete Process using available proxy images. Replace - Replace external references with image data during processing. AttemptReplacement - Attempt to replace external references with image data during processing. If replacement fails, complete the Process using available proxy images. |
||
|
Reduces the resolution of images with a resolution higher than MaxResolution . Replaced with a link to ImageCompressionParams in the Process. |
||
|
Specifies the minimum resolution that an image must have in order to be embedded. If not specified, images of any resolution can be embedded. |
||
|
Identifies the mechanism used for reducing the image resolution. Deprecation note: starting with JDF 1.1, use a link to ImageCompressionParams in the Process. |
||
|
Identifies a set of filename extensions that will be trimmed during searches for high-resolution images. These extensions are what will be stripped from the end of an image name to find a base name. The leading dot “.” is included. The values are examples: |
||
|
Identifies how many levels of recursion in the search path will be traversed while trying to locate images. A value of 0 indicates that no recursion is desired. |
||
|
Specification of the paths to search when trying to locate the referenced data. The FileSpec replaces the SearchPath text element. |
||
|
String that identifies the paths to search when trying to locate the referenced data. |
7.2.97 ImageSetterParams
This Resource specifies the settings for the imagesetter. A number of settings are OEM-specific, while others are so widely used they may be supported between vendors. Both filmsetter settings and platesetter settings are described with this Resource.
|
Additional media advancement beyond the media dimensions on a Web-Fed Device. |
||
|
Size of the burnout area. The area defined by BurnOutArea is exposed, regardless of the size of the image. If not specified or "0 0" , only the area defined by the image is exposed. |
||
|
Specifies the axis around which a Device is to center an image if the Device is capable of doing so. FeedDirection - Image is centered around the feed-direction axis. |
||
|
This Attribute specifies the axis around which a Device must mirror an image if the Device is capable of doing so. None - Do not mirror the image. FeedDirection - Image is mirrored around the feed-direction axis. |
||
|
The width in points of the bottom margin measured inward from the edge of the Media with respect to the idealized Process coordinate system of the ImageSetting Process. The Media origin is unaffected by NonPrintableMarginBottom . These margins are independent of the PDL content. |
||
|
Same as NonPrintableMarginBottom except for the left margin. |
||
|
Same as NonPrintableMarginBottom except for the right margin. |
||
|
If "true" , indicates that the Device must create registration punch holes. Use a Combined Process with a Bending Process to specify punching in JDF 1.3 and beyond. |
||
|
Name of the registration punch scheme, (e.g., Bacher ). Use a Combined Process a Bending Process to specify punching in JDF 1.3 and beyond. |
||
|
Resolution of the output. If not specified, the default is taken from the resolution of the input ByteMap. |
||
|
Sides = "OneSidedFront" New in JDF 1.2 |
Indicates whether the content layout is to be imaged on one or both sides of the media. Sides must not be used unless ImageSetterParams describes output to a proofer. Values are from: Table 7-224, “Sides Attribute Values”. |
|
|
When proofing in a “RIP once, output many” (ROOM) workflow, SourceWorkStyle specifies the direction in which the bytemaps have been prepared for press. The Device is to use this information to calculate a transformation that results in a proof that is identical to the press Sheet |
||
|
Media ? |
Describes the media to be used. Different Media may be specified in different Partition leaves to enable content driven Media selection. |
|
|
Describes the hardware image fitting algorithms. Allows printing even if the size of the imageable area of the media does not match the requirements of the data. |
-- Attribute: Sides
7.2.98 Ink
Resource describing what kind of ink or other colorant (e.g., toner, varnish) is to be used during printing or varnishing. The default unit of measurement for Ink is Unit = “ g ” (gram).
FountainNumber , Separation , SheetName , Side , SignatureName , WebName
ConventionalPrinting , DigitalPrinting , Varnishing
|
Link to a definition of the color specifics. The value of ColorName color should match the Name Attribute of a Color defined in a ColorPool Resource that is linked to the Process that is using the Ink Resource. Instead of linking the ColorPool Resource directly, it may be referenced by another Resource that is linked to the Process. Note: A ColorName Attribute is used differently in other Resources where it refers to a NamedColor as defined in Section A.3.3.3, “NamedColor” . Deprecation note: starting with JDF 1.4, use Separation Partition Key. |
||
|
ISO - ink [ISO2846-1:1997] (used by SWOP) Varnish - liquid that is similar to ink |
||
|
The fully qualified ink name including the ink Family name. For instance, "PANTONE 138 C" is is a member of the PANTONE family. |
||
|
Modification note: starting with JDF 1.4, the data type was expanded from NMTOKEN to NMTOKENS. |
||
7.2.99 InkZoneCalculationParams
This Resource specifies the parameters for the InkZoneCalculation Process.
|
Even number of positions. Each pair specifies the begin and end of the ink slides belonging to a certain fountain. The positions are in coordinates of the printable width along the cylinder axis. The first pair is associated to the first fountain position (corresponds to the Partition FountainNumber = "0") , the second to the second position ( FountainNumber = "1" ), etc. |
||
|
Position and size of the printable area of the print cylinder in the coordinates of the Preview Resource. The Partition TileID must be used for each plate together with this Attribute in case of multiple plates per cylinder. Multiple plates per cylinder may be used in Web Printing. The default case is to specify a rectangle that encompasses the complete image to be printed. |
||
|
The width of one zone in the feed direction of the printing Machine being used. |
||
|
The width of one zone of the printing Machine being used. Typically, the width of a zone is the width of an ink slide. |
||
|
Device ? |
Device provides a reference to the press that the InkZoneProfile is defined for and is used to gather information about ink zone geometry. |
7.2.100 InkZoneProfile
This Resource specifies ink zone settings that are specific to the geometry of the printing Device being used. InkZoneProfile Elements are independent of the Device details.
FountainNumber , Separation , SheetName , Side , SignatureName, WebName
7.2.101 InsertingParams
This Resource specifies the parameters for the Inserting Process. Figure 7.13 shows the various components involved in an inserting Process, and how they interact.
The process coordinate system is defined as follows: The Y-axis is aligned with the binding edge and increases from the registered edge to the edge opposite the registered edge. The X-axis, meanwhile, is aligned with the registered edge. It increases from the binding edge to the edge opposite the binding edge, which is the product front edge.
|
Finished Page number of the mother Component on which the child Component has to be placed. FinishedPage must not be specified unless InsertLocation = "FinishedPage" . Corresponds to Folio on InsertingIntent . |
||
|
Where to place the “child” Sheet. FinishedPage - Place the child exactly onto the page specified in FinishedPage . New in JDF 1.2 Overfold - Place onto the overfold. Replaces OverfoldLeft and OverfoldRight . New in JDF 1.2 OverfoldLeft - Deprecated in JDF 1.2 OverfoldRight - Deprecated in JDF 1.2 Modification note: starting with JDF 1.2, this Attribute is renamed from Location due to a name clash with the Location Partition Key. |
||
|
Offset between the Sheet to be inserted and the “mother” Sheet. SheetOffset is implied by the Transformation matrix in ResourceLink /@ Transformation of the child’s ComponentLink . |
||
|
GlueLine * |
Array of all GlueLine Elements. The coordinate system is defined by the mother Component . |
The following graphics depict the various values of InsertingParams /@ InsertLocation:
7.2.102 InsertSheet
InsertSheet Resources define Device generated images and Sheets which can be produced along with the Job. InsertSheet Elements include separators Sheets, error Sheets, accounting Sheets and Job Sheets. The information provided on the Sheet depends on the type of Sheet. In some cases, an Imposition Process can encounter RunList Elements that do not provide enough finished pages to complete a Layout Resource or its children. InsertSheet Resources are used to provide a standard way of completing such Layout Resources. InsertSheet Resources may also be used to start new Sheet Resources, (e.g., to ensure that a new chapter starts on a right-hand page). In addition, InsertSheet may specify whether new media are to be inserted after the current Sheet, Signature, Instance Document or Job is completed.
InsertSheet Elements may be used at the beginning or end of RunList with a SheetUsage Attribute of "Header" or "Trailer" . When an InsertSheet appears both in a RunList and in a Layout , the following precedence applies:
- 1 The InsertSheet with Usage FillSurface from the RunList is applied first.
- 2 The InsertSheet with Usage FillSheet from the RunList is applied.
- 3 The InsertSheet with Usage FillSignature from the RunList is applied.
- 4 After completely processing the RunList InsertSheet Elements once, apply the Layout Partition’s InsertSheet Elements.
If the RunList of the InsertSheet does not supply enough content to fill a Sheet, Signature or surface, the RunList will be reapplied until no PlacedObject slots remain to be filled. When an InsertSheet is used in a RunList of a Process that does not use a Layout or LayoutPreparationParams Resource (i.e., that Process is not a part of a Combined Process with Imposition or LayoutPreparation ), only Usage "Header" or "Trailer" are valid.
Disjointing , LayoutPreparationParams , RunList
|
Defines bundle items when this InsertSheet is not a Subelement of RunList . If this InsertSheet is a Subelement of a RunList , then IncludeInBundleItem must be ignored, and RunList / @EndOfBundleItem must be used instead. As an example, IncludeInBundleItem controls whether the InsertSheet is to be included in a bundle item for purposes of finishing the InsertSheet with other Sheets. After - This InsertSheet is to be included in the BundleItem that occurs after this InsertSheet . "After" is equivalent to "None" if no BundleItem is defined after this InsertSheet Before - This InsertSheet is to be included in the BundleItem that occurs before this InsertSheet . "Before" is equivalent to "None" if no BundleItem is defined before this InsertSheet . None - This InsertSheet is not included in a BundleItem . New - A new BundleItem is created. This InsertSheet will be in the new BundleItem by itself unless another InsertSheet with IncludeInBundleItem = "Before" occurs immediately after this InsertSheet . |
||
|
Specifies whether the InsertSheet is waste that is to be removed from the document before further processing. If "true" , the InsertSheet is to be discarded when finishing the document. |
||
|
List of marks that are to be marked on this InsertSheet . Ignored if a Sheet is specified in this InsertSheet . |
||
|
Identifies that Device-dependent information is to be included on the InsertSheet . Duplicate - Valid for SheetUsage = "Interleaved" or "InterleavedBefore" . Specifies that the interleaved Sheet is to contain the same (duplicate) content as the previous ( "Interleaved") or following ( "InterleavedBefore" ) Sheet. If there is content on both sides of the previous or following Sheet (duplex), then the InsertSheet has both sides duplicated. New in JDF 1.2 |
||
|
AccountingSheet - A Sheet that reports accounting information for the Job. ErrorSheet - A Sheet that reports errors for the Job. FillSheet - A Sheet that fills ContentObject Elements with no matching entry in the content RunList . InsertSheet - A Sheet that is inserted to the Job, (e.g., a preprinted cover). JobSheet - A Sheet that delimits the Job. SeparatorSheet - A Sheet that delimits pages, sections, copies or Instance Documents of the Job. |
||
|
Indicates where this InsertSheet is to be produced and inserted into the set of output pages. Values are from: Table 7-231, “SheetUsage Attribute Values”. |
||
|
Layout ? |
Details of the Sheet that will be inserted. Contents for this Layout are drawn from the RunList included in this InsertSheet if any. If not specified, the system specified insert Sheets are used. Any InsertSheet Resources referenced by this Layout are ignored. |
|
|
RunList ? |
A RunList that provides the content for the InsertSheet . Any InsertSheet Resources referenced by this RunList are ignored. |
|
|
Sheet ? |
Details of the Sheet that will be inserted. Contents for this Sheet are drawn from the RunList included in this InsertSheet if any. If not specified, the system specified insert Sheets are used. Any InsertSheet Resources referenced by this Sheet are ignored. Deprecation note: starting with JDF 1.3, use Layout . |
-- Attribute: SheetUsage
|
Valid for SheetType = "FillSheet" . Contents of the RunList of the InsertSheet are used to fill the next Finished front Page of the current Sheet before forcing the next page of the content RunList to the next Finished back Page if not already on a Finished back Page. Modification note: starting with JDF 1.4, this value applies to Finished pages rather than sheet surfaces. |
|
|
Valid for SheetType = "FillSheet" . Contents of the RunList of the InsertSheet are used to fill the next Finished back Page of the current Sheet before forcing the next Page of the content RunList to the next Finished front Page if not already on a Finished front Page. A typical use is to start a chapter on the front side of the Finished Page. Modification note: starting with JDF 1.4, this value applies to Finished pages rather than sheet surfaces. |
|
|
Valid for SheetType = "FillSheet" . Contents from the RunList of the InsertSheet are used to fill the current Sheet. |
|
|
Valid for SheetType = "FillSheet" . Contents from the RunList of the InsertSheet are used to fill the current Signature. |
|
|
Valid for SheetType = "FillSheet" . Contents from the RunList of the InsertSheet are used to fill the current surface. |
|
|
Valid for SheetType = "InsertSheet" , "JobSheet" or "SeparatorSheet" . The Sheet is produced at the beginning of the Job (for JobSheet), or at the beginning of each copy of each Instance Document (for SeparatorSheet), or is appended before the current Sheet, Signature, layout or RunList as defined by its context. Contents for the Sheet are drawn from the RunList included in this InsertSheet Resource if one is included. If a RunList is not included, the inserted Sheet is filled with system-specified content defined by SheetType . |
|
|
Valid for SheetType = "SeparatorSheet" . The Sheet is produced after each page, (e.g., used to insert Sheets under transparencies). Contents for the Sheet are drawn from the RunList included in this InsertSheet Resource if one is included. If a RunList is not included, the inserted Sheet is filled with system-specified content defined by SheetType = "SeparatorSheet" . |
|
|
Valid for SheetType = "SeparatorSheet" . The Sheet is produced before each page, (e.g., used to insert Sheets before transparencies). Contents for the Sheet are drawn from the RunList included in this InsertSheet Resource if one is included. If a RunList is not included, the inserted Sheet is filled with system-specified content defined by SheetType = "SeparatorSheet" . |
|
|
Valid for SheetType = "ErrorSheet" . The Sheet is produced at the end of the Job only when an error or warning occurs. |
|
|
Valid for SheetType = "SeparatorSheet" . The Sheet is produced between each copy of each Instance Document. Contents for the Sheet are drawn from the RunList included in this InsertSheet Resource if one is included. If a RunList is not included, the inserted Sheet is filled with system-specified content defined by SheetType = "SeparatorSheet" . |
|
|
Valid for SheetType = "SeparatorSheet" . The Sheet is produced between each copy of the Job, which is defined to be when the complete RunList has been consumed. Contents for the Sheet are drawn from the RunList included in this InsertSheet Resource if one is included. If a RunList is not included, the inserted Sheet is filled with system-specified content defined by SheetType = "SeparatorSheet" . |
|
|
Valid for SheetType = "AccountingSheet" , "ErrorSheet" , "InsertSheet" , "JobSheet" and "SeparatorSheet" . The Sheet is produced at the end of the Job (for "AccountingSheet" , "ErrorSheet" and "JobSheet") , or at the end of each copy of each Instance Document (for "SeparatorSheet" ), or is appended after the current Sheet, Signature, layout or RunList as defined by its context. Contents for the Sheet are drawn from the RunList included in this InsertSheet Resource if one is included. If a RunList is not included, the inserted Sheet is filled with system specified content defined by SheetType. Note: use SheetType = "ErrorSheet" and SheetUsage = "Trailer" to always produce a Sheet that contains error or success information even if no errors or warnings occurred. |
7.2.103 InterpretedPDLData
Represents the results of the Interpreting or RasterReading Process. The details of this Resource are not specified, as it is assumed to be implementation dependent.
7.2.104 InterpretingParams
The InterpretingParams Resource contains the parameters needed to interpret PDL pages. The Resource itself is a generic Resource that contains Attributes that are relevant to all PDLs. PDL-specific instances of InterpretingParams Resources may be included as Subelements of this generic Resource. This specification defines one additional PDL-specific Resource instance: PDFInterpretingParams .
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
|
Indicates whether or not the finished page image is to be centered within the imageable area of the media. The Center is ignored if FitPolicy /@ SizePolicy = "ClipToMaxPage" and clipping is specified. |
||
|
Specifies whether the finished page contents is to be scaled to fit the media. In JDF 1.1 and beyond, use FitPolicy . |
||
|
This Attribute specifies the axis around which a RIP is to mirror an image. Note that this is mirroring in the RIP and not in the hardware of the output Device. FeedDirection - Image is mirrored around the feed-direction axis. |
||
|
The image must be RIPed in the specified polarity. Note that this is a polarity change in the RIP and not a polarity change in the hardware of the output Device. |
||
|
Specifies whether the page contents is to be expanded such that each page covers X by Y pieces of media. |
||
|
This pair of real numbers identifies the amounts of overlap in points for the poster tiles across the horizontal and vertical axes, respectively. |
||
|
Generic switch for setting the quality of an otherwise inaccessible Device. High - Highest quality available on the printer. |
||
|
A pair of positive real values that indicates the scaling factor for the page contents. Values between 0 and 1 specify that the contents are to be reduced, while values greater than 1 specify that the contents are to be expanded. This Attribute is ignored if FitToPage = "true" or if Poster is present and has a value other than "1 1 ". Any scaling defined in FitPolicy must be applied after the scaling defined by this Attribute. |
||
|
A pair of real values that identifies the point in the unscaled PDL page that remains at the same position after scaling. This point is defined in the coordinate system of the PDL page. For example, The ScalingOrigin of a PDL page with dimensions "300 400" scaled from the PDL page center would be "150 200" , regardless of the value of Scaling . Modification note: starting with JDF 1.4, 1) the default value MAY be set to an implementation defined value; the default value is no longer specified as "0 0" in this document; 2) the phrase “PDL page” replaces “Page”; 3) this attribute specifies the point which is not shifted when scaling is applied and doesn’t specify a new Origin, i.e. lower left of the page. |
||
|
Allows printing even if the size of the imageable area of the media does not match the requirements of the data. This replaces the deprecated FitToPage Attribute. This FitPolicy Resource must be ignored in a Combined Process with LayoutPreparation . |
||
|
Media * |
This Resource provides a description of the physical media which will be marked. The physical characteristics of the media may affect decisions made during Interpreting . The cardinality was changed to “*” in JDF 1.2 in order support description of multiple media types, (e.g., Film, Plate and Paper.) If multiple Media are specified, Media /@ MediaType defines the type of Media . If multiple Media with Media /@ MediaType = "Paper" are specified in a proofing environment, the first Media is the proofer paper and the second Media is the final Device paper. |
|
|
Indicates the resolution at which the PDL contents will be interpreted in DPI. These Elements may be different from the ObjectResolution Elements provided in the Resource. |
||
|
Details of interpreting for PDF. Note that this is a Subelement in JDF 1.1 and beyond, and not an instance as in JDF 1.0. |
7.2.104.1 Element: PDFInterpretingParams
|
Indicates whether BlackGeneration functions are to be emitted. |
||
|
Indicates whether UnderColorRemoval functions are to be emitted. |
||
|
Indicates whether or not overprint settings in the file will be honored. If "true" , the setting for overprint will be honored. If "false" , it is expected that the Device does not directly support overprint and that the PDF is preprocessed to simulate the effect of the overprint settings |
||
|
Indicates whether colors specified by ICC color spaces are to be treated as Device colorants. |
||
|
Specifies whether optional Content Groups (OCGs or layers) in the PDF being interpreted and not explicitly listed in subsidiary OCGControl Subelements, are to be included in the InterpretedPDLData produced by the Interpreting Process. Exclude - All layers not explicitly listed are to be excluded. FromPDF - The guidelines in the PDF reference are to be used to determine whether to include each layer that is not explicitly listed. Include - All layers not explicitly listed are to be included. |
||
|
If OCGDefault = "FromPDF" , then the value of OCGIntent sets the intent for which OCGs are to be selected. Design - as described in [PDF1.6] . View - as described in [PDF1.6] . |
||
|
If OCGDefault = "FromPDF" , then the value of OCGProcess sets the purpose for which the Interpreting Process is being performed. This, in turn, sets which value from a relevant optional content usage dictionary is to be used to determine whether each OCG is included in the InterpretedPDLData : Export - PDF ExportState in the Export subdictionary. |
||
|
If OCGDefault = "FromPDF" , then the value of OCGZoom sets the magnification to be assumed in comparisons with the Zoom dictionary in a relevant optional content usage dictionary to determine whether each OCG is included in the InterpretedPDLData . A OCGZoom value of 1.0 is assumed to be a magnification of 100%. |
||
|
Indicates whether the contents of annotations on PDF pages MUST be included in the output. This only refers to annotations that are set to print in the PDF file excluding trap annotations. Trap annotations are controlled with PrintTrapAnnotations . |
||
|
Indicates whether the contents of trap annotations on PDF pages MUST be included in the output. |
||
|
Values are 0 to 1. A value of 0 represents the lowest allowable quality; 1 represents the highest desired quality. |
||
|
Provides a list of the OCGs (layers) that are to be explicitly included or excluded in the InterpretedPDLData . Any OCGs not listed in an OCGControl Element will follow the rules set by OCGDefault . |
7.2.104.2 Element: OCGControl
|
Defines whether the optional content group(s) identified by OCGName are to be included in the InterpretedPDLData . If "true" , then the layer must be included. If "false" , it must not . Note that the contents stream of excluded OCGs must still be interpreted so that changes to CTM, etc., are acted on. The objects drawn in excluded OCGs must not be rendered. |
||
|
The name of the optional content group(s) that must be included or excluded. Note that the Name Attribute of an optional content group entry is encoded as a PDF text string, and OCGName is encoded with the Unicode variant identified in the JDF file header; names must be re-encoded as necessary for comparison. Using a value for OCGName that does not match any OCG in the referenced PDF file is an error (subject to SettingsPolicy ), independent of the value of IncludeOCG . |
7.2.104.3 More about PDFInterpretingParams
7.2.104.3.1 PDF Optional Content Groups
The order of OCGControl Elements has no effect; the Z-order of graphic elements that make up each optional content group (the term layer is misleading in this regard) within the PDF file defines the drawing order of those graphic elements.
Any preferences recorded in OCGs within the PDF file as to whether that OCG are to be displayed or not will be ignored if that OCG is referenced from an OCGControl Element, or if OCGDefault is either "Include" or "Exclude" ; PDF preferences are only applied when OCGDefault = "FromPDF" .
If OCGDefault = "FromPDF" , the state of all OCGs explicitly referenced from OCGControl Elements must be set before determining the state of any remaining OCGs.
All controls for OCGs in JDF address OCGs directly, and not optional Content Member Dictionaries (OCMDs do not have unique names).
NOTE: [PDF1.6] does not state that all OCGs must have unique names. It is therefore possible for a single PDF file to contain multiple OCGs with the same name. When OCGControl /@OCGName refers to multiple OCGs in a file, they will all be explicitly included or excluded together.
7.2.105 JacketingParams
Description of the setup of the jacketing machinery. Jacket height and width (1 and 4 in the Figure 7-40) are specified within the Component that describes the jacket.
|
|
7.2.106 JobField
A JobField is a Mark object that specifies the details of a Job. The JobField Elements are also referred to as slug lines.
Layout / MarkObject , LayoutPreparationParams , StrippingParams / StripMark
|
A formatting string used with JobTemplate to generate a string. Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
A list of values used with JobFormat to generate a string. Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
Text from the operator. Note that this was erroneously described as text to the operator in JDF 1.1 and below. Constraint : starting with JDF 1.4, if JobFormat and JobTemplate are specified, ShowList , OperatorText and UserText MUST NOT be specified. |
||
|
List of elements to display in the JobField . Constraint : starting with JDF 1.4, if JobFormat and JobTemplate are specified, ShowList OperatorText and UserText MUST NOT be specified. Values include those from: Table I-1, “Predefined variables used in @XXXTemplate and @ShowList”. New in JDF 1.4 Modification note: starting with JDF 1.4, the values come from a common list rather than a list that is custom to this Resource. In addition, ShowList becomes optional. |
||
|
User-defined text to output with JobField . Constraint : starting with JDF 1.4, if JobFormat and JobTemplate are specified, ShowList , OperatorText and UserText MUST NOT be specified. |
||
|
DeviceMark defines the formatting parameters for the mark. If not specified, the settings defined in LayoutPreparationParams / DeviceMark are assumed. Deprecation note: starting with JDF 1.4, DeviceMark MUST be specified in the parent MarkObject Element. |
7.2.107 LabelingParams
LabelingParams defines the details of the Labeling Process.
7.2.108 LaminatingParams
This Resource specifies the parameters needed for laminating.
|
Type of adhesive used. Valid only when LaminatingMethod = DispersionGlue . |
||
|
List of non-laminated gap positions in the X direction of the laminating tool in the coordinate system of the Component . The zero-based even entries define the absolute position of the start of a gap, and the odd entries define the end of a gap. If not specified, the complete area defined by LaminatingBox is laminated. |
||
|
Type of hardener used. Valid only when LaminatingMethod = "DispersionGlue" . |
||
|
Area on the Component to be laminated. |
||
|
Width of the nip in points to be formed between the fusing rollers and the component in the Laminating Process. |
||
|
Temperature used in the Laminating Process, in ˚ Centigrade. |
7.2.109 Layout
Represents the root of the layout structure. The Layout is used both for fixed-layout and for automated printing.
LayoutIntent , Component , CylinderLayout , InsertSheet
SignatureName , WebName , RibbonName , SheetName , Side , PartVersion
ConventionalPrinting , CylinderLayoutPreparation , DigitalPrinting , Imposition , InkZoneCalculation
|
If "true" , the Imposition Process is expected to perform automated imposition. Layout /@ Automated MUST only be specified in the root Partition of Layout . Default value is: "false" in the root Partition of Layout |
||
|
Policy about how the Ord Attribute of an entry MUST be calculated when extracting a page from a RunList and positioning it in the Layout . PagePool - The Base Ord is reset to point to the first page entry of the Page Pool at the beginning of each Page Pool processed by the Imposition Template . PagePoolList - At the beginning of processing of the Imposition Template , the Base Ord is reset to point to the first page entry of the first Page Pool to be processed by the Imposition Template . This results in all Page Pool s that will be processed by the Imposition Template to be treated as a Page Pool List . |
||
|
Determines the relationship of the coordinate systems for front and back surfaces. When "false" , all contents for all surfaces are transformed into the first quadrant, in which the origin is at the lower left corner of the surface. When "true" , contents for the front surface are imaged into the first quadrant (as above), but contents for the back surface are imaged into the second quadrant, in which the origin is at the lower right. This allows the front and back origins to be aligned even if the exact media size is unknown. The LockOrigins was copied from the deprecated Sheet Resource. |
||
|
Maximum number of Sheets that will be collected into a signature. MaxCollect modifies the pagination when automated imposition is selected. Specifying MaxCollect can effectively cause a Page Pool or Page Pool List to be broken into “sub” Page Pools. Each of these “sub” Page Pools provides the set of pages mapped onto a single Collect, and are processed sequentially out of the “parent” Page Pool (or Page Pool List). Thus each sub-Page Pool effectively restarts the ord counting within the Imposition Template (i.e. treat a sub-Page Pool as if a new Page Pool were being started with the Imposition Template). |
||
|
Zero-based maximum number of Instance Documents that are consumed from a RunList each time the Layout is executed, assuming the Imposition Process is automated. |
||
|
Zero-based maximum number of placed objects that are consumed from a RunList each time the Layout is executed, assuming the Imposition Process is automated. If not specified, it must be calculated from the Ord values of the ContentObject Elements in the Layout . Deprecation note: MaxOrd has no meaning if negative Ord values exist in an automated Layout . The consumer MUST calculate the implied 2 values for increasing and decreasing the explicit Ord values in an automated Layout by evaluating the actual values of ContentObject /@ Ord . Increment from Front = 1+max( ContentObject /@ Ord _+) where “ Ord _+” specifies positive values of Ord ; Decrement from Back = max (abs (( ContentObject /@ Ord _-)) where “ Ord _-” specifies negative values of Ord . See ref automated Layout for details. |
||
|
Zero-based maximum number of Document Sets that are consumed from a RunList each time the Layout is executed, assuming the Imposition Process is automated. |
||
|
Minimum number of Sheets that will be collected into a signature. MinCollect modifies the pagination when automated imposition is selected. |
||
|
Unique name of the Layout . The Name is used for external reference to a Layout . Deprecation note: starting with JDF 1.4, use DescriptiveName . |
||
|
Range of Ord values of the RunList ( Document ) that are consumed by this Layout section. MUST NOT be specified unless @ Automated = "true" . |
||
|
Policy as to when the automated imposition variables SheetCount and TotalSheetCount are reset. See Section 6.4.17.2, “Variables for Automated Imposition”. Continue - SheetCount continues to increment for each sheet generated by the current Imposition Template . PagePool - SheetCount is reset to zero upon start of processing of a new Page Pool and TotalSheetCount is determined for that new Page Pool ..
PagePoolList
-
SheetCount
is reset to zero upon start of processing of an
Imposition Template
, and
TotalSheetCount
is recalculated. |
||
|
A formatting string used with SheetNameTemplate to algorithmically construct SheetName . SheetNameFormat and SheetNameTemplate are used to identify individual parts of the Layout in an automated environment. Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
A list of values used with SheetNameFormat to algorithmically construct SheetName . SheetNameFormat and SheetNameTemplate are used to identify individual parts of the Layout in an automated environment. Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
Indicates which WorkStyle was used to create the Layout . This is only informative and can be useful when creating double sided proofs. |
||
|
This box, specified in Layout -coordinate space, defines the area into which MarkObject or ContentObject Elements are distributed. The lower left corner of the rectangle specified by the value of this Attribute establishes the coordinate system into which the content is mapped and should have a value of "0 0" . SurfaceContentsBox may imply clipping. This Attribute should be supplied in order to get predictable placement of content. If this Attribute is not supplied, a rectangle with the origin at "0 0" and an extent that may be dependent on the dimensions of one of the Media is implied. |
||
|
Additional Sheets that are to be inserted before and/or after a document. Depending on which Partition level the InsertSheet is defined, it specifies how to complete the Sheet or surface in an automated printing environment. Deprecation note: starting with JDF 1.4, use Layout / PageCondition for "FillSheet" , "FillSurface" , and "FillSignature" operations; use Layout / SheetCondition for an insert sheet. |
||
|
List of LayerDetails Elements. |
||
|
When specified, configures the imposition engine to place content onto one or more Logical Stack s distributed on a common set of sheets. Layout / LogicalStackParams MUST only be specified in the root Layout element AND only when Layout /@ Automated = "true" . All Logical Stack s defined by LogicalStackParams MUST be used in all Imposition Template s. See Section 6.4.17.4.1, “Using Logical Stacks”. |
||
|
Media * |
Describes the media to be used. If multiple Media are specified, Media / @MediaType species the type of Media , typically Paper, Plate or Film. Multiple Media with the same Media /@ MediaType must not be specified in one Layout . Note that at least one Media must be specified in the Partitioned Layout tree in JDF 1.3 or above. |
|
|
Describes the media to be used. Replaced by Media in JDF 1.1. |
||
|
The PageCondition Elements are used only with automated imposition. They define restrictions on which page content may be placed in a Layout / ContentObject and. If any PageCondition restricts placing a page into a ContentObject , the Page MUST NOT be filled into that ContentObject . |
||
|
Provides a list of the ContentObject and MarkObject Elements to be placed on to the surface. Contains the marks on the surface in rendering order. All PlacedObject Elements must be specified in the Partition leaves of the Layout . See Section 7.2.109.12.1.2, “Position of PlacedObject Elements in Layout” . Note: PlacedObject is not a container but an Abstract type. |
||
|
Specifies the conditions under which the optional sheet defined by this Layout is produced. MUST only be present when Layout /@ Automated = "true" , and MUST be contained within a Layout branch partitioned by SheetName . |
||
|
The Signature Element has been replaced by a Layout Partition, namely Layout [@ SignatureName ]. In JDF 1.3 and beyond, Signature / @Name has been replaced by the Partition Key Layout / @SignatureName . |
||
|
Describes the relationship of transfer curves and coordinate systems within the various Processes. |
7.2.109.1 Element: LayerList
This Element provides a container for an ordered list of LayerDetails Elements. The individual Elements are referenced by their zero-based index in the LayerList using the LayerIDs Partition Key.
7.2.109.2 Element: LayerDetails
This Element provides information about individual layers.
7.2.109.3 Element: LogicalStackParams
|
Maximum number of imposed sheets to generate as an Imposed Sheet Set (the size of the Logical Stack ). Implementations MUST generate the minimum stack size to accommodate the available number of Logical Sheet s if the total number of required sheets for the last stack is smaller than MaxStackDepth . |
||
|
Describes any restrictions set on the placement of a Recipient Set 's Logical Sheet s within or across Imposed Sheet Set s. None - a recipient set's Logical Sheet s may be placed across both Logical Stack s and Imposed Sheet Set s. WithinImposedSheetSet - a Recipient Set 's Logical Sheet s MUST be placed within a single Imposed Sheet Set WithinLogicalStack - a Recipient Set 's Logical Sheet s MUST be placed within a single Logical Stack . |
||
|
Stack + |
Describes parameters to control the sequencing of Logical Sheet s onto individual Logical Stack s. |
7.2.109.4 Element: Stack
|
0-based Logical Stack identifier that specifies which Logical Stack is controlled by this Stack Element. The value of Stack /@ LogicalStackOrd MUST correspond to a PlacedObject /@ LogicalStackOrd value. |
||
|
Specifies how Logical Sheet s MUST be placed onto the Logical Stack . SheetIndex - Logical Sheet s are placed in the order of ascending SheetIndex . DescendingSheetIndex - Logical Sheet s are placed in the order of descending SheetIndex . |
7.2.109.5 Element: PageCondition
The PageCondition Element defines restrictions on when page content MUST NOT be placed in a ContentObject of a Layout . Before placing page content from a RunList into a ContentObject the PageCondition /@ RestrictedContentObjects Attribute MUST be checked for the Ord of the ContentObject . If the Ord of the ContentObject is in the RestrictedContentObjects Attribute Value, the alternate content, if any, MUST be placed in the ContentObject . After skipping a restricted ContentObject , the Imposition Process MUST then place the current page content into the location defined by the next ContentObject (after that specified by the RestrictedContentObject ). This corresponds to incrementing the effective Ord value of the page in the RunList by 1, effectively incrementing the total number of pages of the RunList . If the next ContentObject is also restricted then the process is repeated. PageCondition Elements are processed in their XML order.
|
List of @ Ord values of those ContentObject Elements into which page content that matches the conditions as specified in Part or PageCondition /@ Condition MUST NOT be placed. |
||
|
Specifies the conditions when the PageCondition applies. Condition MUST NOT be specified if Part Elements are present. PagePoolStart - the condition is true when the Ord refers to the first page of a Page Pool in the RunList . PagePoolEnd - after processing of the Page Pool is completed, the condition is true for all unused Ord positions in the current Collect. PagePoolListStart - the condition is true when the Ord refers to the first page of an aggregated set of Page Pool s in the RunList . PagePoolListEnd - after processing of the Page Pool list is completed, the condition is true for all unused Ord positions in the current Collect. |
||
|
RunList ? |
Alternate page content that MUST be placed into the ContentObject Elements that are specified in RestrictedContentObjects when the PageCondition evaluates to "true" . The first page of the referenced RunList MUST be used. |
|
|
Part * |
Specifies the conditions when the PageCondition applies. Multiple Part Elements specify alternate page conditions (ORing of them). Part Elements MUST NOT be specified if Condition is present. |
Example 7-23: PageCondition
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< Layout Class = "Parameter" ID = "L000004" Status = "Available"
PartIDKeys = "SheetName Side" >
< PageCondition RestrictedContentObjects = "1 -1" >
<!-- Force document with Chapter starts onto a right hand side (facing)
< Part DocTags = "Chapter" DocRunIndex = "0" />
< Layout SheetName = "Mysheet" >
< ContentObject CTM = "1 0 0 1 0 0" Ord = "-1" /> <!-- Outside left -->
< ContentObject CTM = "1 0 0 1 595 0" Ord = "0" /> <!-- outside right -->
< ContentObject CTM = "1 0 0 1 0 0" Ord = "1" /> <!-- inside left-->
< ContentObject CTM = "1 0 0 1 595 0" Ord = "-2" /> <!-- inside right-->
<LayoutLink Usage="Input" rRef="L000004"/>
7.2.109.6 Element: SheetCondition
|
When present, defines an optional sheet by specifying each condition (equivalent to a logical or) under which the optional sheet is produced. Begin - At beginning of imposition processing (all sets in case of multiple Recipient Set s) End - At the end of imposition processing. BeginSet - At beginning of processing of an individual Recipient Set . EndSet - At end of processing of an individual Recipient Set . PagePoolBegin - At beginning of processing of a Page Pool . PagePoolEnd - At the end of processing of a Page Pool . PagePoolListBegin - At beginning of processing of a Page Pool List PagePoolListEnd - At end of processing of a Page Pool List LogicalStackBegin - adds a Logical Sheet to the beginning of each Logical Stack generated as part of an Imposed Sheet Set . LogicalStackEnd - adds a Logical Sheet to the end of each Logical Stack generated as part of an Imposed Sheet Set . LogicalStackSetBegin - At beginning of generation of a set of Logical Stack s. Note that LogicalStackOrd MUST be used to indicate the Logical Stack on which the conditional sheet is placed. LogicalStackSetEnd - At end of generation of a set of Logical Stack s. Note that LogicalStackOrd MUST be used to indicate the Logical Stack on which the conditional sheet is placed. ImposedSheetSetBegin - At beginning of generation of an Imposed Sheet Set . Note that this generates a separator sheet not counted as part of the Imposed Sheet Set . Any MarkObject Elements specifying LogicalStackOrd are ignored. ImposedSheetSetEnd - At end of generation of an Imposed Sheet Set . Note that this generates a separator sheet not counted as part of the Imposed Sheet Set . Any MarkObject Elements specifying LogicalStackOrd are ignored. |
||
|
RunList ? |
Supplies content for any ContentObject Elements specified within the optional sheet definition. All ContentObject Elements in the optional sheet definition MUST reference content supplied by this RunList . |
7.2.109.7 Element: PlacedObject
The marks that are to be placed on the designated surface of a Layout come in two varieties: ContentObject or MarkObject Elements. All inherit characteristics from the Abstract PlacedObject which is described below.
7.2.109.7.1 Element: Abstract PlacedObject
|
Specifies the anchor point of the PlacedObject that remains in place on the surface when the value of TrimSize changes. Anchor is specified in the coordinate system of the PlacedObject prior to application of the CTM . |
||
|
Clipping rectangle in the coordinates of the SurfaceContentsBox . ClipBox MUST NOT be present if PlacedObject /@ ClipBoxFormat is supplied. |
||
|
A formatting string used with ClipBoxTemplate to algorithmically construct ClipBox . ClipBoxFormat MUST ONLY be present if PlacedObject /@ ClipBox is not supplied and Layout /@ Automated = "true" . Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
A list of values used with ClipBoxFormat to algorithmically construct ClipBox . ClipBoxTemplate MUST ONLY be present if PlacedObject /@ ClipBox is not supplied and Layout /@ Automated = "true" . Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
Clip path for the PlacedObject in the coordinates of the SurfaceContentsBox (lower left of SurfaceContentsBox is used as reference zero point, same as for ClipBox ). The actual clip region is the union of ClipBox and ClipPath or the union of ClipBox and SourceClipPath . ClipPath and SourceClipPath must not be specified in the same PlacedObject . ClipPath should be specified when both ClipPath and SourceClipPath are known because ClipPath provides a more stable coordinate system (not sensitive to shifts caused by editing the page). |
||
|
A formatting string used with CompensationCTMTemplate to algorithmically construct a compensation CTM that MUST be concatenated to CTM. CompensationCTMFormat MAY be present if Layout /@ Automated = "true" . Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
A list of values used with CompensationCTMFormat to algorithmically construct a compensation CTM that MUST be concatenated to CTM. CompensationCTMTemplate MAY be present if Layout /@ Automated = "true" . Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
The coordinate transformation matrix (CTM -- a Postscript term) of the object in the SurfaceContentsBox . For details, see Figure 2-8, “Equation for Surface Coordinate System Transformations” . The origin of the source coordinate system is the lower left (expressed in the source coordinate system) of the object and the origin of the destination coordinate system is lower left of the SurfaceContentsBox . For details, see Section 2.5.1.1, “Source Coordinate Systems” . Note: CTM must be recalculated if the object is replaced afterwards with a new object with different dimensions. |
||
|
Location of the origin for screening of this ContentObject . Specified in the coordinate systems of SurfaceContentsBox . |
||
|
If a Layout supports layering (e.g., for versioning), LayerID specifies the index of the Layout / LayerList / LayerDetails Element in Layout / LayerList that a ContentObject belongs to, (e.g., the language layer version). The details of the layers are specified in the Layout / LayerList / LayerDetails Element. |
||
|
0-based Logical Stack identifier that this PlacedObject belongs to. LogicalStackOrd MUST match the LogicalStackOrd of an entry in Layout / LogicalStackParams / Stack . |
||
|
If a Layout supports layering (e.g., for versioning), elements that belong to the same final page SHOULD have a matching OrdID . |
||
|
Clip path for the PlacedObject in the source coordinate system. SourceClipPath is applied to the referenced source object in addition to any clipping that is internal to the object. Internal transformation of the source object (Rotation key in PDF, Orientation Tag in TIFF etc.) MUST be applied prior to applying SourceClipPath. ClipPath and SourceClipPath must not be specified in the same PlacedObject . See Section 2.5.1.1, “Source Coordinate Systems” for definitions of source coordinate systems. |
||
|
The die cutting path for the PlacedObject in the coordinates of the SurfaceContentsBox (lower left of SurfaceContentsBox is used as reference zero point, same as for ClipBox ). That path can be used for proofing purpose. |
||
|
The transformation matrix of the trim box to be applied to the object’s referenced content in the coordinate system of SurfaceContentsBox . Note that imposition programs that execute the Layout MUST recalculate the CTM in case the referenced content is replaced with new referenced content having different dimensions, otherwise the position of the content inside the trim box will shift. This recalculation is based on Anchor , TrimCTM , TrimSize and trim box. |
||
|
The size of the object's trim box as viewed in the SurfaceContentsBox ( TrimCTM scaling and rotation applied). TrimSize is needed when replacing the object by a new object with a different dimension. Note: Recalculation of PlacedObject / @CTM is only necessary when the Imposition Process needs to replace some pages from the provided RunList (using the Layout as a kind of imposition template). To ensure correct placement of a new page in the Layout , PlacedObject / @CTM recalculations should always be done according to PlacedObject / @TrimCTM and PlacedObject / @TrimSize . Together, these two Attributes represent the trimming information of the imposition software page, which is not always the same as the original RunList page trimming information (= LayoutElement / @SourceTrimBox when real trim box of the object is known). Usage of both PlacedObject Elements TrimCTM and TrimSize Attributes will allow page replacements on any type of imposition Layout . |
||
|
Describes the kind of PlacedObject . |
||
|
MUST NOT be present when Layout /@ Automated = "false" . Specifies automated fit policy for the page cell described by the PlacedObject . When present, PlacedObject /@ TrimSize MUST also be present in the PlacedObject , and represents the cell size for this PlacedObject . |
7.2.109.8 Element: ContentObject
ContentObject Elements describe containers for page content on a surface. They are filled from the content RunList of the Imposition Process. For print applications where page count varies from Instance Document to Instance Document, imposition templates can automatically assign pages to the correct surface and PlacedObject position.
|
Reference to an index of an Instance Document in the content RunList . This references an Instance Document with an index module. Layout /@ MaxDocOrd equals DocOrd in an automated layout scenario. The index can either be known explicitly from a variable RunList or implicitly from the index within an indexable content definition language, (e.g., PPML). |
||
|
A zero-based reference to an index in the content RunList . The index is incremented for every page of the RunList with IsPage = "true" . The Ord value of the first page of a RunList has the value "0" . If Layout /@ Automated = "true" , Ord MAY be a negative integer in a ContentObject . In this case, the explicit Ord for each iteration of the automated Layout is calculated by subtracting the appropriate number of Ord values from the back of the document. For details on automated Layout , see Section 6.4.17, “Imposition”. |
||
|
Function to calculate an Ord value dynamically, using a value of s for Signature number and n for total number of pages in the Instance Document. The Ord or DocOrd and OrdExpression are mutually exclusive in one PlacedObject . Value format is from: Section 7.2.109.12.5, “Using Expressions in the OrdExpression Attribute”. |
||
|
A non-negative, zero-based reference to an index of a Document Set in the content RunList . This references an Instance Document with an index module. Layout /@ MaxSetOrd = SetOrd in an automated layout scenario. The index can either be known explicitly from a variable RunList or implicitly from the index within an indexable content definition language, (e.g., PPML). |
7.2.109.9 Element: MarkObject
MarkObject Elements describe containers for page marks on a surface. The PDL for the marks should exist prior to imposing and should be filled from the RunList ( Marks ) of the Imposition Process. An individual MarkObject represents the content data of the Marks. The content data in individual MarkObject Elements may contain multiple logical marks.
|
ContentRef refers to the ContentObject that this MarkObject is related to. ContentRef is used to define the object that metadata for generating dynamic marks MAY be extracted from. |
||
|
Page number to use from the PDL file described by LayoutElement . Modification note: starting with JDF 1.3, the default value of "0" is removed. Deprecation note: starting with JDF 1.4, PDL for Marks MUST be referenced via RunList ( Marks ). |
||
|
A non-negative reference to an index in the RunList ( Marks ). The index is incremented for every page of the RunList with IsPage = "true" . The first page of a RunList has the value 0. Modification note: starting with JDF 1.4, at most one of Ord or DeviceMark MUST be specified. For JDF 1.3 only, at most one of LayoutElement , Ord or JobField MUST be specified. |
||
|
Specific information about this kind of mark object. See below for information regarding dynamically generated marks. |
||
|
Specific information about this kind of mark object. See below for information regarding dynamically generated marks. |
||
|
CutMark * |
Specific information about this kind of mark object. See below for information regarding dynamically generated marks. |
|
|
Specific information about this kind of mark object. See below for information regarding dynamically generated marks. |
||
|
DeviceMark specifies all formatting options for dynamic Marks JobField / DeviceMark specifies the formatting parameters of the JobField and all other dynamically generated marks are positioned with CTM . Constraint: at most one of Ord or DeviceMark MUST be specified. Creation note: starting with JDF 1.4, DeviceMark is back after being deprecated in JDF 1.3. |
||
|
Definition of text replacement for a MarkObject . MarkObject / DynamicField specifies text replacement within an existing PDL mark. |
||
|
Specific information about this kind of mark object. See below for information regarding dynamically generated marks. |
||
|
JobField ? |
JobField specifies the metadata of a given dynamic slug line. Modification note: starting with JDF 1.4, the maximum number of JobField Elements per MarkObject is limited to 1; previously, there was no limit. For JDF 1.3 only, at most one of LayoutElement , Ord or JobField should be specified. |
|
|
PDL description of the mark. The LayoutElement and Ord are mutually exclusive within one MarkObject . Modification note: for JDF 1.3 only, at most one of LayoutElement , Ord or JobField MUST be specified. Deprecation note: starting with JDF 1.4, PDL for Marks MUST be referenced via RunList ( Marks ). |
||
|
Rules about when to apply the mark in an automated Layout . If no MarkActivation is specified, the MarkObject is unconditionally active. If multiple MarkActivation Elements are specified, all conditions MUST be met for the mark to be active. MarkActivation MUST NOT be specified unless Layout /@ Automated = "true" . |
||
|
Details of the coordinate system that this mark is placed relative to. This MAY be either the sheet coordinate system or the coordinate system of a referenced PlacedObject . If the anchor point in the referenced object ( PlacedObject or Sheet surface) is modified, e.g. due to a change in TrimSize , the CTM of the placed object of this DeviceMark MUST be modified accordingly. Note: RefAnchor does NOT modify the origin of the CTM of this PlacedObject . It is only used to recalculate relative shifts. |
||
|
Specific information about this kind of mark object. See below for information regarding dynamically generated marks. |
||
|
Specific information about this kind of mark object See below for information regarding dynamically generated marks. |
7.2.109.10 Element: MarkActivation
MarkActivation specifies condition when to apply the mark in an automated Layout .
|
The context in which the iteration is counted. CollectSheetIndex - a parameter maintained by the imposition engine to count sheets (e.g. in the context of a signature). Its value starts at 0 and is incrmented by one for each sheet. If Layout /@ MaxCollect is specified, its maximum value is one less than Layout /@ MaxCollect . Otherwise, it continues to increment per sheet until completion of the page-pool/page-pool-list processing through the Imposition Template . See Section 6.4.17, “Imposition”. SetDocIndex - a Partition Key. SubDocIndex0 , ... - a parameter maintained by the imposition engine. See Section 6.4.17, “Imposition”. |
||
|
The enclosing MarkObject is active and its specified Mark MUST be imaged if the value of the variable specified by Context is equal to one of the values of this Attribute. |
7.2.109.10.1 Dynamic Marks
JobField , LayoutElement and Ord are mutually exclusive within one MarkObject .
The Elements marked as Dynamic marks in the table above can be used for three purposes:
- If one Ord or LayoutElement is specified, the PDL of the mark is provided by the RunList ( Marks ) or LayoutElement and the dynamic mark Subelements provide metadata about the mark to a press Controller or bindery equipment. This is the usual behavior of existing imposition engines. A single MarkObject must not contain multiple mark Subelements that are represented by the same PDL, for instance there may be only one Marks layer for an entire surface.
- If neither Ord nor LayoutElement is present, but JobField is present, an Imposition Device should dynamically generate a slug line based on information in JobField .
- If none of Ord , LayoutElement and JobField are present, a mark should be dynamically drawn based on the information within the Subelement. The marks are positioned relative to the CTM of the MarkObject . A single MarkObject should not contain multiple dynamic mark Subelements. Note that the JDF specification of dynamic marks other than JobField are in flux and that the behavior described here might change in future versions of JDF.
7.2.109.11 Element: DynamicField
DynamicField provides a description of dynamic text replacements for a MarkObject Element. This Element is to be used for production purposes such as defining bar codes for variable data printing. DynamicField Elements are not intended as a placeholders for actual content such as addresses. Rather, they are marks with dynamic data such as time stamps and database information. Dynamic objects are MarkObject Elements with additional optional DynamicField Elements that define text replacement.
|
Format string in C printf format that defines the replacement. Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
String that must be replaced by the DynamicInput Element in the Contents RunList referenced by Ord or OrdExpression . |
||
|
Reference to an index in the Contents RunList that contains DynamicInput Elements. Constraint: at most one of Ord or OrdExpression must be specified. Deprecation note: starting with JDF 1.4, Ord MUST be specified in the parent MarkObject Element. |
||
|
Expression to calculate the reference to an index in the Contents RunList that contains DynamicInput fields. Values include those from: ContentObject /@ OrdExpression Constraint: at most one of Ord or OrdExpression must be specified. |
||
|
String that must be replaced by the instantiated text expression as defined by the Format and Template Attributes in the file referenced by MarkObject / Ord , MarkObject / OrdExpression or MarkObject / LayoutElement . If ReplaceField is not specified, the Device that processes the DynamicField must format the DynamicField . |
||
|
Template to define a sequence of variables consumed by Format . Values are from: Appendix I, “Generating strings with Format and Template” . Deprecation note: starting with JDF 1.4, RunList / DynamicInput /@ Name (mentioned here in JDF 1.3) no longer defines further variables because DynamicInput has been deprecated. |
||
|
DeviceMark defines the formatting parameters for the mark. If not specified, the DeviceMark settings defined in LayoutPreparationParams or in the Layout tree are assumed. |
Example 7-24: Layout: DynamicField Element
In this example, the text “ ___xxx___ ” in the file MyReplace.pdf would be replaced by the sentence “Replacement Text for Joe and John go in here at 14:00 on Mar-31-2000 ”. MyReplace.pdf is placed at the position defined by the CTM of the MarkObject and Variable.pdf is placed at the position defined by the CTM of the ContentObject .
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< RunList Class = "Parameter" ID = "L3" PartIDKeys = "Run" Status = "Available" >
< MetadataMap DataType = "String" Name = "i1" ValueFormat = "%s"
<!--This expression maps the value of /Dokument/Rezipient/@Name to a
< Expr Name = "s1" Path = "/Dokument/Rezipient/@Name" />
< LayoutElement ElementType = "Graphic" >
< FileSpec URL = "File:///Variable.pdf" />
< Layout Class = "Parameter" ID = "Link0003" Status = "Available" >
<!--The MarkObject in the Layout hierarchy: -->
< ContentObject CTM = "1 0 0 1 0 0" Ord = "0" />
< MarkObject CTM = "1 0 0 1 10 10" >
< LayoutElement ElementType = "Graphic" >
< FileSpec URL = "File:///MyReplace.pdf" />
Format = "Replacement Text for %s goes in here at %s on %s"
Ord = "0" ReplaceField = "___xxx___" Template = "i1,Time,Date" />
< DynamicField Format = "More Replacement Text for %s go in here"
Ord = "0" ReplaceField = "___yyy___" Template = "SignatureName" />
<LayoutLink Usage="Input" rRef="Link0003"/>
<RunListLink Usage="Input" rRef="L3"/>
7.2.109.12 More about Layout
7.2.109.12.1 Migrating from a Pre-JDF 1.3 Layout to a Partitioned Layout
The Layout Resource was significantly modified in JDF 1.3. This section describes how a pre-JDF 1.3 Layout can be transformed into a JDF 1.3 Layout and what restrictions MAY be applied to a JDF 1.3 Layout so that it can be easily transformed into a pre-JDF 1.3 Layout or a PJTF Layout.
Note: this section is not applicable when Layout /@ Automated = "true" for any Partitions.
7.2.109.12.1.1 Partition Key restrictions:
If "SignatureName" , "SheetName" or "Side" are specified in PartIDKeys, the order must be specified as "SignatureName SheetName Side" .
Only a Layout with exactly PartIDKeys = "SignatureName SheetName Side" can be translated into a JDF 1.2 Layout or a PJTF. Thus, it is highly recommended to use exactly this Partitioning of the Layout in JDF 1.3 whenever possible. Any other Partitioning will make consumption by existing products very unlikely.
7.2.109.12.1.2 Position of PlacedObject Elements in Layout
In order to avoid ambiguities in the layering order, MarkObject Elements and ContentObject Elements must only be specified in the leaves of Partitioned Resources.
Example 7-25: Invalid MarkObject
The following INVALID example is correct according to Section 3.10.5.1, “Subelements in Partitioned Resources” . If standard Partitioning inheritance were permitted for MarkObject Elements and ContentObject Elements it would be unclear whether the ContentObject in Sheet01 is layered over or under < MarkObject Ord = "1" >:
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< Layout Class = "Parameter" ID = "L3" Status = "Available"
PartIDKeys = "SignatureName SheetName Side" >
<!-- INVALID, this PlacedObject is not in a leaf partition and not used -->
<!-- since it is overwritten by <MarkObject Ord="1"> -->
< MarkObject Ord = "0" CTM = "0.0 1.0 -1.0 0.0 176.69 23.62" >
< RegisterMark Center = "0.0 0.0" MarkType = "Cross" MarkUsage = "PaperPath" />
< Layout SignatureName = "Sig00" >
<!-- INVALID, this PlacedObject is not in a leaf partition -->
< MarkObject Ord = "1" CTM = "0.0 1.0 -1.0 0.0 176.69 23.62" >
< RegisterMark Center = "0.0 0.0" MarkType = "Cross"
< Layout SheetName = "Sheet00" >
< MarkObject Ord = "2" CTM = "0.0 1.0 -1.0 0.0 176.69 23.62" >
< RegisterMark Center = "0.0 0.0" MarkType = "Arc"
< ContentObject CTM = "0.0 1.0 -1.0 0.0 176.69 23.62" Ord = "0" />
< Layout SheetName = "Sheet01" >
<!-- Not clear whether this is layered over or under
< ContentObject CTM = "0.0 1.0 -1.0 0.0 176.69 23.62" Ord = "0" />
Example 7-26: MarkObject
This VALID example is contains the same PlacedObject Elements as the previous example but they are correctly specified in the leaves of the Partitioned Layout .
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< Layout Class = "Parameter" ID = "L3" Status = "Available"
PartIDKeys = "SignatureName SheetName Side" >
< Layout SignatureName = "Sig00" >
< Layout SheetName = "Sheet00" >
< MarkObject Ord = "2" CTM = "0.0 1.0 -1.0 0.0 176.69 23.62" >
< RegisterMark Center = "0.0 0.0" MarkType = "Arc"
< ContentObject CTM = "0.0 1.0 -1.0 0.0 176.69 23.62" Ord = "0" />
< Layout SheetName = "Sheet01" >
< MarkObject Ord = "1" CTM = "0.0 1.0 -1.0 0.0 176.69 23.62" >
< RegisterMark Center = "0.0 0.0" MarkType = "Cross"
< ContentObject CTM = "0.0 1.0 -1.0 0.0 176.69 23.62" Ord = "0" />
<LayoutLink Usage="Input" rRef="L3"/>
7.2.109.12.2 CTM Definitions
The following are explanations of the terms used in this section and beyond:
- Dimensions of object - The width and height of either the box defined to include all drawings for this file format, or the artificial box that includes these drawings for file formats that have no clearly defined box for this.
- Trim box of the Signature page - A rectangle that indicates where the trim box of object is to be positioned. This is the equivalent to the area the user is intended to see in the final product. Positioning the trim box of the object inside the trim box of the Signature page is implementation-specific (usually it is centered).
- Trim box of the object - A rectangle that is PDL-specific that indicates the area of the object that indicates the intended trimming area.
7.2.109.12.3 Finding the Trim Box of an Object
The LayoutElement / @SourceTrimBox always takes precedence over boxes defined inside the file. Make sure that LayoutElement /@ SourceTrimBox is updated after replacing Elements. The following is a list of names used for the real trim box in various file formats:
- PostScript (PS) - PageSize
- Encapsulated PostScript (EPS) - CropBox
- Portable Document Format (PDF) - TrimBox
- Raster files - entire area
If this information is not available, alternative sources for trim box information can include (but these boxes might not be correct in all cases):
7.2.109.12.4 Using Ord to Reference Elements in RunList Resources
The Ord Attribute in ContentObject or MarkObject Elements represents a reference to a logical element in a RunList . The index is incremented for every page of the RunList with IsPage = "true" . The reference is not changed by repartitioning the RunList . The content and marks RunList are referenced independently. The following examples illustrate the usage of Ord .
Example 7-27: RunList: Simple Multi-File Unseparated RunList
This example specifies all pages contained in File1.pdf and File2.pdf. File 1 has 6 pages, file 2 has an unknown number of pages.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< RunList Class = "Parameter" ID = "L3" PartIDKeys = "Run" Status = "Available" >
< RunList NPage = "6" Pages = "0 ~ 5" Run = "1" >
< FileSpec URL = "File:///File1.pdf" />
< RunList Pages = "0 ~ -1" Run = "2" >
< FileSpec URL = "File:///File2.pdf" />
<RunListLink Usage="Input" rRef="L3"/>
Example 7-28: RunList: Simple Multi-File Separated RunList
This example specifies two pages contained in Presep.pdf and following that, pages 1, 3 and 5 of each preseparated file.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< RunList Class = "Parameter" ID = "Link0003" PartIDKeys = "Run Separation"
< RunList NPage = "2" Run = "1" SkipPage = "3" >
< FileSpec URL = "File:///Presep.pdf" />
< RunList FirstPage = "0" IsPage = "false" Separation = "Cyan" />
< RunList FirstPage = "1" IsPage = "false" Separation = "Magenta" />
< RunList FirstPage = "2" IsPage = "false" Separation = "Yellow" />
< RunList FirstPage = "3" IsPage = "false" Separation = "Black" />
< RunList IsPage = "true" Pages = "1 3 5" Run = "2" >
< RunList IsPage = "false" Separation = "Cyan" >
< FileSpec URL = "File:///Cyan2.pdf" />
< RunList IsPage = "false" Separation = "Magenta" >
< FileSpec URL = "File:///Magenta2.pdf" />
< RunList IsPage = "false" Separation = "Yellow" >
< FileSpec URL = "File:///Yellow2.pdf" />
< RunList IsPage = "false" Separation = "Black" >
< FileSpec URL = "File:///Black2.pdf" />
<RunListLink Usage="Input" rRef="Link0003"/>
7.2.109.12.5 Using Expressions in the OrdExpression Attribute
Expressions can use the operators +, -, *, /,% and parentheses, operating on integers and two variables: s for Signature number (starting at 0) and n for number of pages to be imposed in one document. Signature number denotes the number of times that a complete set of placed objects has been filled with content from the run list. The operators have the same meaning as in the C programming language. Expressions are evaluated with normal “C” operator precedence. Multiplication must be expressed by explicitly including the * operator, (i.e., use “2*s” , not “2 s” ). Remainders are discarded.
Example 7-29: OrdExpression
Saddle stitched booklet for variable page length documents.
The following describes the OrdExpressions for a booklet with varying page lengths. The example page assignments are for a book of 13-16 pages.
OrdExpression = ì4*((n+3)/4) ñ(s*2)-1 15 13 11 9
Example 7-30: DocOrd Usage
Two-sided business cards 4/Sheet
The following describes the Ord + DocOrd usage for a 4-up step + repeat business card
7.2.109.13 Element: Signature
The table defining the deprecated Signature Subelement has been moved to Section P.4.7.1, “Signature” . All Attributes that were defined in Signature have been moved into Layout .
7.2.110 LayoutElement
This Resource is needed for LayoutElementProduction . It describes some text, an image, one or more pages or anything else that is used in the production of the layout of a product.
LayoutElement / Dependencies , LayoutElementProductionParams / LayoutElementPart , RunList
DBDocTemplateLayout , DBTemplateMerging , LayoutElementProduction , ShapeDefProduction
DBDocTemplateLayout , LayoutElementProduction
|
Path that describes the outline of the LayoutElement in the coordinate space of the LayoutElement of ElementType = "Page" that results from the LayoutElementProduction Process. The default case is that there is no clip path. ClipPath , SourceClipBox , PlacedObject /@ SourceClipPath and PlacedObject /@ ClipBox if supplied, must be concatenated. |
||
|
IDs of ContentData Elements in the referenced ContentList . ContentData Elements provide Metadata related to the product to be published. ContentDataRefs MUST NOT be specified if no ContentList is specified. |
||
|
Describes the content type for this LayoutElement . Values are from: Table 7-254, “ElementType Attribute Values”. |
||
|
If "true" , the file has bleeds. If not specified, the set of values of PageList / PageData /@ HasBleeds selected by PageListIndex is applied. |
||
|
If "true" , any PDL defined imposition definition must be ignored. Examples are PDF with embedded PJTF or PPML with a PRINT_LAYOUT . If IgnorePDLImposition = "false" and JDF also defines imposition, the imposed Sheets of the PDL are treated as pages in the context of JDF imposition. The front and back surfaces of the PDL and JDF imposition should be matched. Note that it is strongly discouraged to specify imposition both in the PDL and JDF, and that this might result in undesired behavior. |
||
|
If "true" , the LayoutElement has no content marks and is blank. If not specified, the set of values of PageList / PageData /@ IsBlank selected by PageListIndex is applied. Note that in JDF 1.2 the description erroneously stated that IsBlank = "false" specifies a blank page. |
||
|
If "true" , the file is a PDL file and can be printed. Possible files types include PCL, PDF or PostScript files. Application files such as MS Word have IsPrintable = "false" . If not specified, the set of values of PageList / PageData /@ IsPrintable selected by PageListIndex is applied. |
||
|
If "true" , the file has been trapped. If not specified, the set of values of PageList / PageData /@ IsTrapped selected by PageListIndex is applied. |
||
|
List of the indices of the PageData Elements of the PageList specified in this LayoutElement . Note that this list may be overridden by the RunList that contains this LayoutElement and refers to a subset of this LayoutElement . PageList must be specified if PageListIndex is specified. |
||
|
A rectangle that describes the bleed area of the element to be included. This rectangle is expressed in the source coordinate system of the object. If not specified, the set of values of PageList / PageData /@ SourceBleedBox selected by PageListIndex is applied. |
||
|
A rectangle that defines the region of the element to be included. This rectangle is expressed in the source coordinate system of the object. If not specified, the set of values of PageList / PageData /@ SourceClipBox selected by PageListIndex is applied. |
||
|
The MediaBox of the LayoutElement . |
||
|
A rectangle that describes the intended trimmed size of the element to be included. This rectangle is expressed in the source coordinate system of the object. If not specified, the set of values of PageList / PageData /@ SourceTrimBox selected by PageListIndex is applied. |
||
|
Template is "false" when this layout element is self-contained. This Attribute is "true" if the LayoutElement represents a template that must be completed with information from a database. If not specified, the value of PageList / PageData /@ Template is applied. |
||
|
ContentList with additional metadata. Constraint: at most one of ContentList and PageList MUST be specified. |
||
|
List of dependent references, (e.g., fonts, external images, etc.). |
||
|
Color details of the LayoutElement . If not specified, the value of PageList / PageData / ElementColorParams is applied. |
||
|
FileSpec ? |
URL plus metadata about the physical characteristics of a file representing the LayoutElement . If not present, then only metadata is known but not the content file. |
|
|
Specification of the image compression properties. If not specified, the value of PageList / PageData / ImageCompressionParams is applied. |
||
|
PageList ? |
Specification of page metadata for pages described by this LayoutElement . Constraint: at most one of ContentList and PageList MUST be specified. |
|
|
Specification of the screening properties. If not specified, the value of PageList / PageData / ScreeningParams is applied. |
||
|
List of used separation names. If not specified, the value of PageList / PageData / SeparationSpec is applied. |
-- Attribute: ElementType
7.2.110.1 Element: Dependencies
This Element provides a container for dependent references of the LayoutElement .
|
Description of dependent elements, (e.g., fonts, images, etc.). |
7.2.111 LayoutElementProductionParams
This Resource is needed for LayoutElementProduction . This Resource contains detailed information about the type of LayoutElement to be produced. In JDF 1.3 it only contains information for automated production of barcodes. The description of positioning of the graphics has been added in JDF 1.4.
|
A pool of Action Elements that describe the restrictions that are applied to the created output |
||
|
Description of the specific parameters for generating a LayoutElement . |
||
|
ShapeDef ? |
A resource describing the shape of the LayoutElement to be produced. |
|
|
TestPool ? |
Container for zero or more Test elements that are referenced from Action Elements in the ActionPool . TestPool MUST be supplied if ActionPool is present. |
Example 7-31: LayoutElementProductionParams: Page Shape
<? xml version = "1.0" encoding = "UTF-8" ?>
A page with a certain size -->
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID = "n001"
Type = "LayoutElementProduction"
Status = "Waiting" DescriptiveName = "Page sample for shape"
JobPartID = "ID34" Version = "1.4" >
< LayoutElementProductionParams Class = "Parameter" ID = "LEPParams"
< LayoutElement Class = "Parameter" ID = "LayElOut" Status = "Unavailable"
SourceMediaBox = "0 0 595.27 822.05"
SourceTrimBox = "28.34 28.34 566.93 793.71" />
< LayoutElementProductionParamsLink rRef = "LEPParams" Usage = "Input" />
< LayoutElementLink rRef = "LayElOut" Usage = "Output" />
< Created Author = "XYZ Corporation" TimeStamp = "2006-01-09T09:00:00+01:00" />
Example 7-32: LayoutElementProductionParams: Label Shape
<? xml version = "1.0" encoding = "UTF-8" ?>
<!-- Shape Sample for a label with a cut line
Date: Jan 9, 2005 Version: 1.00
A page with a certain size -->
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID = "n001"
Type = "LayoutElementProduction"
Status = "Waiting" DescriptiveName = "Page sample for shape"
JobPartID = "ID400" Version = "1.4" >
< LayoutElementProductionParams Class = "Parameter" ID = "LEPParams"
< Shape ShapeType = "Path" DDESCutType = "101" CutPath = "..." />
</ LayoutElementProductionParams >
< LayoutElement Class = "Parameter" ID = "LayElOut" Status = "Unavailable"
SourceMediaBox = "0 0 595.27 822.05"
SourceTrimBox = "28.34 28.34 566.93 793.71" />
< LayoutElementProductionParamsLink rRef = "LEPParams" Usage = "Input" />
< LayoutElementLink rRef = "LayElOut" Usage = "Output" />
< Created Author = "ABC-Corporation" TimeStamp = "2006-01-09T09:00:00+01:00" />
Example 7-33: LayoutElementProductionParams: Box Shape
<? xml version = "1.0" encoding = "UTF-8" ?>
<!-- Shape Sample for a box defined by a CAD file
Date: Jan 9, 2005 Version: 1.00
A page with a certain size -->
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID= "n001"
Type = "LayoutElementProduction"
Status = "Waiting" JobPartID = "ID100"
DescriptiveName = "Page sample for shape" Version = "1.4" >
< LayoutElementProductionParams Class = "Parameter" ID = "LEPParams"
< FileSpec URL = "file://myserver/myshare/olive.dd3" />
</ LayoutElementProductionParams >
< LayoutElement Class = "Parameter" ID = "LayElOut" Status = "Unavailable" />
< LayoutElementProductionParamsLink rRef = "LEPParams" Usage = "Input" />
< LayoutElementLink rRef = "LayElOut" Usage = "Output" />
< Created Author = "ZYX Corporation" TimeStamp = "2006-01-09T09:00:00+01:00" />
7.2.111.1 Element: LayoutElementPart
LayoutElementPart is a generic placeholder for specifying details of LayoutElementProduction . In JDF 1.3 only details of barcode production have been fleshed out but additional Processes are anticipated. Note that the ordering of LayoutElementPart Elements might become significant in future versions.
|
ID of the LayoutElementPart . |
||
|
Description of the specific parameters for barcode production. |
||
|
Specification of an existing LayoutElement that is used to initially populate this LayoutElementPart . Any LayoutElement Resources that are specified here MUST also be specified as Input Resources to the LayoutElementProduction Process. |
||
|
Definition of the size and position of this LayoutElementPart |
7.2.111.2 Element: BarcodeProductionParams
BarcodeProductionParams describes of the specific parameters for barcode production.
|
Description of the formatting and reproduction parameters for barcode production. |
||
7.2.111.3 Element: PositionObj
PositionObj describes the size and position of the LayoutElementPart .
|
Anchor specifies the origin (0,0) of the coordinate system in the unrotated LayoutElementPart . |
||
|
Transformation matrix of the origin of LayoutElementPart as specified by @ Anchor . Not that this is not necessarily the actual CTM that will position a given LayoutElementPart . The actual CTM MUST be recalculated based on the values of Anchor and Size . |
||
|
Reader Page index in the PageList . |
||
|
Specifies the level of freedom when applying the values specified in PositionObj . Exact - The values MUST be followed precisely. Free - The values are used as guidance and MAY be modified by the designer. |
||
|
Specifies the size of the unrotated and unscaled object, relative to the parent specified in RefAnchor . |
||
|
Specifies the level of freedom when applying the values specified in PositionObj . Exact - The values MUST be followed precisely. Free - The values are used as guidance and MAY be modified by the designer. |
||
|
Specifies the size of the unrotated and unscaled object, in points. |
||
|
Specifies the level of freedom when applying the values specified in PositionObj . Exact - The values MUST be followed precisely. Free - The values are used as guidance and MAY be modified by the designer. |
||
|
Reference to a LayoutElementPart that this LayoutElementPart is positioned relative to. If RefAnchor is not specified, PositionObj refers to the lower left of the first page specified in page Range. |
Example 7-34: LayoutElementProductionParams: PositionObj
<? xml version = "1.0" encoding = "UTF-8" ?>
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID = "n000002"
JobPartID = "n000002" Status = "Waiting" Type = "LayoutElementProduction"
xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
xsi:type = "LayoutElementProduction" >
<!--Generated by the CIP4 Java open source JDF Library version :
CIP4 JDF Writer Java 1.3 BLD 46-->
< Created AgentName = "CIP4 JDF Writer Java" AgentVersion = "1.3 BLD 46"
Author = "CIP4 JDF Writer Java 1.3 BLD 46" ID = "a000003"
TimeStamp = "2007-09-05T18:20:31+02:00" />
< RunList Class = "Parameter" ID = "r000004" Status = "Unavailable" >
< LayoutElement Class = "Parameter" >
< FileSpec Class = "Parameter" MimeType = "application/pdf" URL = "output.pdf" />
< LayoutElementProductionParams Class = "Parameter" ID = "r000005"
<!--This is a "well placed" CTM defined mark
The anchor defines the 0,0 point to be transformed
The element to be placed is referenced by LayoutElement/FileSpec/URL
< PositionObj Anchor = "BottomLeft" CTM = "1 0 0 1 0 0" PageRange = "0"
< RefAnchor Anchor = "BottomLeft" AnchorType = "Parent" />
< LayoutElement Class = "Parameter" >
< FileSpec Class = "Parameter" MimeType = "application/pdf"
<!--This is a "roughly placed" reservation in the middle of the page-->
< LayoutElementPart ID = "l000006" >
< PositionObj Anchor = "CenterCenter" PageRange = "0" PositionPolicy = "Free" >
< RefAnchor Anchor = "CenterCenter" AnchorType = "Parent" />
< LayoutElement Class = "Parameter" ElementType = "Image" >
Please add an image of a palm tree on a beach here!
<!--This is a "roughly placed" reservation 36 points below the previous
image; NextPosition points from Anchor on this to NextAnchor on next,
i.e. a positive vector specifies that next is shifted in the positive
direction in the parent (in this case page) coordinate system
< PositionObj Anchor = "TopCenter" CTM = "1 0 0 1 0 36"
PageRange = "0" PositionPolicy = "Free" >
< RefAnchor Anchor = "BottomCenter" AnchorType = "Sibling"
< LayoutElement Class = "Parameter" ElementType = "Image" >
Please add an image of a beach ball below the palm tree!
<!--This is a "well placed" CTM defined mark. The anchor defines the
0,0 point used as the RefAnchor for the element to be transformed
< PositionObj Anchor = "LowLeft" CTM = "1 0 0 1 2 3" PageRange = "0"
< RefAnchor Anchor = "BottomLeft" AnchorType = "Parent" />
< PositionObj Anchor = "TopRight" PageRange = "0" PositionPolicy = "Exact" >
< RefAnchor Anchor = "TopRight" AnchorType = "Parent" />
<!--This is a "roughly placed" mark.
The anchor at top right is placed at the right (=1.0) top(=1.0)
position of the page. No rotation is specified
<!--This is a "roughly placed" container for marks
The anchor at top left is defined in the !Unrotated! orientation.
It is placed at the left (=0.0) bottom(=0.0) position of the page.
The text flows bottom to top (=Rotate 90 = counterclockwise)
< LayoutElementPart ID = "l000009" >
< PositionObj Anchor = "TopLeft" CTM = "0 1 -1 0 0 0"
PageRange = "1" PositionPolicy = "Free" >
< RefAnchor Anchor = "BottomCenter" AnchorType = "Parent" />
<!--This is a barcode inside the previous container
The anchor at bottom left is defined in the !Unrotated! orientation.
It is placed at the left (=0.0) bottom(=0.0) position of the container.
< LayoutElementPart ID = "l000010" >
< PositionObj Anchor = "BottomLeft" CTM = "1 0 0 1 0 0" >
< RefAnchor Anchor = "BottomLeft" AnchorType = "Parent" rRef = "l000009" />
<!--This is a disclaimer text inside the previous container
The anchor at top left is defined in the !Unrotated! orientation.
The barcode and text are justified with their top margins and spaced
by 72 points which corresponds to the left of the page because the
container is rotated 90Â˚ AbsoluteSize specifies the size of the
< PositionObj AbsoluteSize = "300 200" Anchor = "TopLeft" CTM = "1 0 0 1 -72 0" >
< RefAnchor Anchor = "TopRight" AnchorType = "Sibling" rRef = "l000010" />
< LayoutElement Class = "Parameter" ElementType = "Text" >
< FileSpec Class = "Parameter"
URL = "file://myServer/disclaimers/de/aspirin.txt" />
<!--This is a "VERY roughly placed" piece of text somewhere on pages 2-3
RelativeSize specifies the size of the object as a ratio of the size
< PositionObj PageRange = "1 ~ 2" RelativeSize = "0.8 0.5" />
< LayoutElement Class = "Parameter" ElementType = "Text" >
< Comment ID = "c000011" Name = "Instructions" >
the image of a palm tree on a beach here!
<!--This is another "VERY roughly placed" piece of text somewhere on
pages 2-3; the text source is the JDF-->
< PositionObj PageRange = "1 ~ 2" />
< LayoutElement Class = "Parameter" ElementType = "Text" >
< Comment ID = "c000012" Name = "TextInput" >
btw. this is unformatted plain text and nothing else!
</ LayoutElementProductionParams >
< RunListLink Usage = "Output" rRef = "r000004" />
< LayoutElementProductionParamsLink Usage = "Input" rRef = "r000005" />
Example 7-35: LayoutElementProductionParams: Preflight
<? xml version = "1.0" encoding = "UTF-8" ?>
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID = "n000002"
JobPartID = "n000002" Status = "Completed" Type = "LayoutElementProduction"
Version = "1.4" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
xsi:type = "LayoutElementProduction" >
<!--Generated by the CIP4 Java open source JDF Library version : CIP4 JDF
< Created AgentName = "CIP4 JDF Writer Java" AgentVersion = "1.3 BLD 47"
Author = "CIP4 JDF Writer Java 1.3 BLD 47" ID = "a000003"
TimeStamp = "2007-10-11T20:23:18+02:00" />
< PhaseTime AgentName = "CIP4 JDF Writer Java"
AgentVersion = "1.3 BLD 47" Author = "CIP4 JDF Writer Java 1.3 BLD 47"
End = "2007-10-11T20:23:23+02:00" ID = "a000020"
Start = "2007-10-11T20:23:21+02:00" Status = "InProgress"
StatusDetails = "Creative Work" TimeStamp = "2007-10-11T20:23:21+02:00" />
< ProcessRun AgentName = "CIP4 JDF Writer Java"
AgentVersion = "1.3 BLD 47" Author = "CIP4 JDF Writer Java 1.3 BLD 47"
Duration = "PT2S" End = "2007-10-11T20:23:23+02:00"
EndStatus = "Completed" ID = "a000024"
Start = "2007-10-11T20:23:21+02:00" TimeStamp = "2007-10-11T20:23:23+02:00" />
< RunList Class = "Parameter" ID = "r000004" Status = "Unavailable" >
< LayoutElement Class = "Parameter" >
< FileSpec Class = "Parameter" MimeType = "application/pdf" URL = "output.pdf" />
< LayoutElementProductionParams Class = "Parameter" ID = "r000005"
< Comment ID = "c000006" Name = "Instruction" >
Add any human readable instructions here
< Action DescriptiveName = "set number of pages to 4" ID = "A000007"
Severity = "Error" TestRef = "T000008" />
DescriptiveName = "set number of separations to 6 on page 0 and 3"
ID = "A000009" Severity = "Error" TestRef = "T000010" >
< PreflightAction SetRef = "T000011" />
DescriptiveName = "separation to black only on page 1 and 2"
ID = "A000012" Severity = "Error" TestRef = "T000013" >
< PreflightAction SetRef = "T000014" />
< Action DescriptiveName = "set TrimBox to 8.5*11 Method 2"
ID = "A000015" Severity = "Error" TestRef = "T000016" >
< PreflightAction SetRef = "T000017" />
DescriptiveName = "Warn when effective resolution<300 dpi"
ID = "A000018" Severity = "Warning" TestRef = "T000019" />
< IntegerEvaluation ValueList = "4" >
< BasicPreflightTest Name = "NumberOfPages" />
< BasicPreflightTest ListType = "UniqueList" MaxOccurs = "6"
MinOccurs = "6" Name = "SeparationList" />
< IntegerEvaluation ValueList = "0 3" >
< BasicPreflightTest Name = "PageNumber" />
< BasicPreflightTest Name = "SeparationList" />
< IntegerEvaluation ValueList = "1 ~ 2" >
< BasicPreflightTest Name = "PageNumber" />
< RectangleEvaluation ValueList = "0 0 612 792" >
< BasicPreflightTest Name = "PageBoxSize" />
< EnumerationEvaluation ValueList = "TrimBox" >
< BasicPreflightTest Name = "PageBoxName" />
< XYPairEvaluation ValueList = "0 0 ~ 300 300" >
< BasicPreflightTest Name = "EffectiveResolution" />
</ LayoutElementProductionParams >
< RunListLink Usage = "Output" rRef = "r000004" />
< LayoutElementProductionParamsLink Usage = "Input" rRef = "r000005" />
7.2.112 LayoutPreparationParams
This Resource provides the parameters of the LayoutPreparation Process, which provides the details of how finished page contents will be imaged onto media. This Resource has a provision for specifying either a multi-up grid of content page cells or an imposition layout of finished pages. The LayoutPreparation also provides means to specify creeping gutters for booklet imposition. In the case where Attributes of LayoutPreparationParams used to explicitly control creep are specified, the MinGutter and GutterPolicy Attributes of FitPolicy , which affect the adjustment of gutter widths, must not be specified.
A multi-up grid of pages can be step and repeated across, down, or through a stack of Sheets in any axis order. Note that for all Resources, the coordinate system for all parameters is defined with respect to the process coordinate system as defined in Section 2.5.3, “Coordinate Systems of Resources and Processes”. The process coordinate system for LayoutPreparation is defined by the Layout Resource coordinate system.
DocIndex , DocRunIndex , RunIndex , SetIndex , SheetName
|
Indicates which finished page edge should be bound. The binding edge is defined relative to the orientation of the page cell containing the first Reader Page in the finished print component with content on it. |
||||||
|
List of marks that are to be marked on each back surface. The appearance of the marks are defined by the Process implementation. For a list of predefined values, see FrontMarkList . |
||||||
|
This parameter specifies horizontal and vertical creep compensation value in points. The first value specifies the creep compensation of all horizontal gutters, and the second value specifies the creep compensation of all vertical gutters. The numbers specify the distance in points by which the respective explicitly creeping gutter either increments (positive values) or decrements (negative values) in width from one Sheet to the next for a given sequence of Sheets related to the same bound component. If not specified, it may be calculated based on the information taken from Media. |
||||||
|
Specifies the order of operations for finishing a bound booklet created from multiple imposed Sheets. The LayoutPreparation Process needs this information in order to completely determine content page distribution onto the sequence of Sheets comprising the pages of a single booklet under consideration of the values of the PageDistributionScheme and FoldCatalog Attributes. FoldGather - The Sheets of a document are first folded according to the value of the FoldCatalog Attribute and then gathered on a pile. Usually applies to finishing of perfect-bound documents. FoldCollect - The Sheets of a document are first folded, according to the value of the FoldCatalog Attribute, and then collected on a saddle. Usually applies to finishing of both perfect-bound and saddle-stitched booklets. Gather - The Sheets of a document are gathered on a pile. No folding is assumed. GatherFold - The Sheets of a document are first gathered on a pile then folded according to the value of the FoldCatalog Attribute. Usually applies to finishing of both perfect-bound and saddle-stitched booklets. |
||||||
|
Description of the type of fold that will be applied to all printed Sheets according to the folding catalog in Figure 7-33, “Fold catalog part 1” and Figure 7-34, “Fold catalog part 2”. Value format is: " Fn-i " where “n” is the number of finished pages and “i” is either an integer, which identifies a particular fold or the letter "X" , which identifies a generic fold. E.g., "F6-2" describes a Z-fold of 6 finished pages, and "F6-X . " describes a generic fold with 6 finished pages. The LayoutPreparation Process uses the fold description specified by this Attribute in the determination of the proper distribution of pages onto the surfaces of the Sheets in the context of the values of both the PageDistributionScheme and FinishingOrder Attributes. If not present, no folding other than the folding that is implied by PageDistributionScheme = "Saddle" is assumed. |
||||||
|
This Attribute specifies the orientation of how the identified fold catalog entry must be interpreted for the purposes of mapping input pages into the imposition layout (not for purposes of performing the folding, if any, or orienting the Sheet). |
||||||
|
List of marks that are to be marked on each front surface. The appearance of the marks are defined by the Process implementation. Values include those from: Table 7-261, “FrontMarkList Attribute Values”. |
||||||
|
Width in points of the horizontal and vertical gutters formed between rows and columns of page cells of a multi-up Sheet layout. The gutter width is defined as the distance between the PageCell /@ TrimSize defined trim boxes of adjacent page cells. The first value specifies the width of all horizontal gutters, and the second value specifies the width of all vertical gutters. If no gutters are defined because either the NumberUp Attribute is not specified or its explicit values are equal to one, this Attribute must be ignored. In the case where a gutter is identified as creeping by either VerticalCreep or HorizontalCreep , then the values of Gutter specify the initial width of explicitly creeping gutters where the gutter width may increment or decrement depending on the CreepValue Attribute. If a value of CreepValue is negative then Gutter must be interpreted as the starting gutter width of the outermost Sheet, otherwise it must be interpreted as the starting gutter width of the innermost Sheet. Gutter is applied in addition to any Border specified in the PageCell . |
||||||
|
Specifies the minimum width in points of explicitly creeping horizontal and vertical gutter(s). If an explicitly creeping gutter shrinks to a width equal to or less than this value, all subsequent gutters must be set to this value. |
||||||
|
Specifies which horizontal gutters creep. The allowed values are zero-based indexes that reference horizontal gutters formed by multiple rows of pages in a multi-up page layout specified by the second value of NumberUp . The value for an entry in this list must be between zero and two (2) less then the second value of NumberUp . If not specified, then horizontal gutters must not creep. Gutters identified by this Attribute are known as explicitly creeping gutters whereas those not identified are known as implicitly creeping gutters. Note: In order preserve the absolute position of the center lines of all gutters across all Sheets, only specify alternating gutters starting with gutter index zero. |
||||||
|
Specifies the initial gutter width in points for implicitly creeping horizontal and vertical gutters. The first number corresponds to horizontal gutters and the second number corresponds to vertical gutters. The particular Sheet to which this initial gutter applies (innermost or outermost) depends upon the polarity of the creep increment specified by CreepValue (see Gutter ). |
||||||
|
Specifies the minimum width in points of implicitly creeping vertical and horizontal gutter(s). If an implicitly creeping gutter shrinks to a width equal to or less than this value, all subsequent gutters must be set to this value. |
||||||
|
Specifies a regular, multi-up grid of PageCell Elements into which content finished pages are mapped. The first value specifies the number of columns of page cells and the second value specifies the number of rows of page cells in the multi-up grid (both numbers are integers). 
The relative positioning of the page cells within the multi-up grid are defined by the explicit or implied values of the Gutter , HorizontalCreep , VerticalCreep and CreepValue Attributes. The distribution of content pages from the content RunList into the page cells is defined by the explicit or implied values of the PageDistributionScheme , PresentationDirection , Sides , FinishingOrder and FoldCatalog Attributes and the implicit number of Sheets comprising the bound component. |
||||||
|
Specifies how finished pages are to be distributed onto a multi-up grid of finished PageCell Elements defined by the values of the NumberUp Attribute. Saddle - Distribute finished pages onto a sequence of one or more imposition layouts in proper order for saddle stitch binding. For this page distribution scheme, creep is to be applied only to odd-numbered vertical gutters where any even-numbered gutters is to automatically creep in the opposite direction. Perfect - Distribute finished pages onto a sequence of one or more Signatures in proper order for perfect binding. For this page distribution scheme, creep is usually not used. Sequential - The finished pages are distributed onto the multi-up layout according to the value of the PresentationDirection Attribute. Note that page distribution ordering for both "Saddle" and "Perfect" also depends upon the implied number of Sheets per finished Component and how the imposed Sheets are to be folded during finishing as well as the order of gathering and folding. Refer to the FoldCatalog and FinishingOrder Attributes. Note: The NumberUp Attribute must always specify a multi-up layout appropriate for a given finished page distribution ordering and FoldCatalog . Setting this Attribute does not imply the multi-up grid dimensions are appropriate for the selected page distribution scheme. Note: In all cases, the order of finished pages as represented by the content RunList must be either in reader order or in an order appropriate for multi-up saddle stitching. Refer to the PageOrder Attribute. |
||||||
|
The assumed ordering of the finished pages in the RunList . Booklet - The finished pages are ordered in the RunList and must be processed exactly in the order as specified by PresentationDirection . NumberUp must still be set to the appropriate value and is not implied by specifying PageOrder = "Booklet" . PageOrder = "Booklet" must not be used in conjunction with FoldCatalog . Reader - The finished pages are in reader order in the RunList . |
||||||
|
Indicates the order in which finished pages will be distributed into the page cells of the NumberUp layout. If PageDistributionScheme = "Saddle" , PresentationDirection applies to sets of two adjacent pages. This allows positioning of multiple page pairs for SaddleStitching onto one Sheet. FoldCatalog - Finished Pages are imaged so that the result is compatible with a finished product produced from the folding catalog as specified in FoldCatalog . XYZ - Permutations of the letters XYZ and xyz so that exactly one of upper or lower case of x, y and z define the order in which finished pages are flowed along each axis with respect to the coordinate system of the front side of the Sheet. The first letter of the triplet specifies the initial axis of flow. The second letter of the triplet specifies the second axis of flow and so on.
Examples: The following table specifies how cells are ordered on a simplex 4-up layout for a 2-Sheet stack depending on PresentationDirection . In each example, the left set of 4 numbers represent the top Sheet and the right set of 4 numbers represent the bottom Sheet of the 2-Sheet stack. |
||||||
|
Orthogonal rotation including the implied translation to be applied to the grid of PageCell Elements on the entire surface relative to the process coordinate system. Rotate90 - 90˚ counterclockwise rotation. Rotate270 - 90˚ clockwise rotation. Note: For details of orthogonal rotations, refer to Table 2-4, “Matrices and Orientation values for describing the orientation of a Component”. If a RotatePolicy value other than "NoRotate" is specified in FitPolicy , the actual rotation specified in Rotate MAY be modified accordingly. Note: A rotation of the grid also rotates the gutters, (i.e., it is applied after all other parameters have been evaluated and applied). |
||||||
|
Indicates whether the content layout is to be imaged on one or both sides of the media. When the content layout consists of multiple input RunList pages to be imposed on a single surface, Sides applies to the entire unfolded Sheet. When a different value for the Sides Attribute is encountered, it must force a new Sheet. However, when the same value for the Sides Attribute is restated for consecutive pages, it is the same as if that restatement was not present. OneSidedBackFlipX - Page content is imaged on the back side of media so that the corresponding page cells back up to a blank front cell when flipping around the X axis. Equivalent to "WorkAndTumble" with a blank front side. OneSidedBackFlipY - Page content is imaged on the back side of media so that the corresponding page cells back up to a blank front cell when flipping around the Y axis. Equivalent to "WorkAndTurn" with a blank front side. OneSidedFront - Page content is imaged on the front side of media. TwoSidedFlipX - Page content is imaged on both the front and back sides of media Sheets so that the corresponding page cells back up to each other when flipping around the X axis. Equivalent to "WorkAndTumble" . TwoSidedFlipY - Page content is imaged on both the front and back sides of media Sheets so that the corresponding page cells back up to each other when flipping around the Y axis. Equivalent to "WorkAndTurn" . |
||||||
|
The number of Sheets in a stack that are processed when imposing down the Z axis. If not specified, the entire Job defines one stack. |
||||||
|
A list of two integers that species how to impose multiple Instance Documents on one Sheet. The first value specifies the document repeats along the X axis, the second value specifies the repeats along the Y axis. Each entry of NumberUp must be an integer multiple of StepRepeat * StepDocs . Positive values define grouped step and repeat whereas negative values define alternating step and repeat. The following examples, where documents are denoted A and B while pages are denoted 1 and 2, have PresentationDirection = "Xyz", NumberUp = "4 4" and StepRepeat = "2 2 1" and StepDocs =: |
||||||
|
A list of three integers that specifies the number of identical pages to impose. The first value specifies the repeats along the X axis, the second value specifies the repeats along the Y axis, and the third value specifies the repeats down the stack -- the Z axis. Each entry of NumberUp must be an integer multiple of StepRepeat * StepDocs. Positive values define grouped step and repeat, whereas negative values define alternating step and repeat. Note that negative values are illegal for the third component, since the total depth of the stack might be unknown. The following examples have PresentationDirection = "Xyz", NumberUp = "4 4" and StepRepeat =: |
||||||
|
This box, specified in Layout coordinate space, defines the area into which PageCell Elements are distributed. The lower left corner of the rectangle specified by the value of this Attribute establishes the coordinate system into which the content is mapped and should have a value of "0 0" . SurfaceContentsBox may imply clipping. This Attribute should be supplied in order to get predicable placement of content. If this Attribute is not supplied, a rectangle with the origin at "0 0" and an extent that may be dependent on the dimensions of the Media is implied. |
||||||
|
Specifies which vertical gutters creep. The allowed values are zero-based indexes that reference vertical gutters formed by multiple columns of pages in a multi-up page layout specified by the first value of NumberUp . The value for an entry in this list must be between zero and two (2) less then the first value of NumberUp . An index value outside of this range is ignored. If not specified then vertical gutters must not creep. Gutters identified by this Attribute are known as explicitly creeping gutters whereas those not identified are known as implicitly creeping gutters. Note: In order preserve the absolute position of the center lines of all gutters across all Sheets, only specify alternating gutters starting with gutter index zero. |
||||||
|
Details how Device-dependent marks are to be generated. If not specified, the marks are Device-dependent. |
||||||
|
Reference to an external imposition template in a proprietary format. LayoutPreparationParams should not contain information that overlaps information specified in ExternalImpositionTemplate . Information specified in LayoutPreparationParams overrides parameters specified in ExternalImpositionTemplate . |
||||||
|
Details how to fit the grid of PageCell Elements onto the SurfaceContentsBox . |
||||||
|
Details how to place the grid of PageCell Elements into the SurfaceContentsBox . ImageShift m ust be applied before any transformations of the grid of PageCell Elements as specified by Rotate or FitPolicy . The reference origin of the grid of page cells is the lower left corner of the trim box of the lower left page cell of the grid of the first Sheet prior to applying any creep. Note that ImageShift will generally be required to allow for space when CreepValue is positive. |
||||||
|
Additional Sheets to be inserted before, after or within a Job. |
||||||
|
JobField * |
||||||
|
Media ? |
||||||
|
PageCell ? |
PageCell Elements describe how page contents will be imaged onto individual page cells. At most one PageCell must be specified and it is applied to all page cells on both surfaces of a Sheet. |
|||||
7.2.112.1 Element: PageCell
|
A number indicating the width in points of a drawn border line, that appears around the trim region specified by the explicit or implied value of TrimSize . A value of "0" specifies no border. If the value of this Attribute is non-zero and positive, then a border of that specified width will be drawn to the outside of the page cell whose inside dimension is the same as the explicit or implied value of the TrimSize Attribute. The border marks must not overwrite the page contents of the trimmed page. Note that when the page cells are distributed evenly over the area of the SurfaceContentsBox , the page cells position and/or size can be adjusted to accommodate the border. If the value of this Attribute is non-zero and negative, then a border of a width specified by the absolute value of this Attribute will be drawn to the inside of the page cell whose outside dimension is the same as the explicit or implied value of the TrimSize Attribute. The border marks may overwrite the page contents of the trimmed page. The rectangle defined by the inside edge of the border defines a ClipBox beyond which no content will be imaged. |
||
|
Defines a rectangle with an origin relative to the lower left corner of the page cell rectangle defined by the explicit or implied value of the TrimSize Attribute. Page content data imaged outside of the region defined by this rectangle must be clipped. If ClipBox is larger than TrimSize , it is used to specify a bleed region. If not specified, its default value is "0 0 X Y" where X and Y are the explicit or implied values of TrimSize . |
||
|
List of marks that are to be marked on each page cell. The appearance of the marks are defined by the Process implementation. |
||
|
Orthogonal rotation to be applied to the contents in each page cell. Rotate90 - 90˚ counterclockwise rotation. Rotate270 - 90˚ clockwise rotation. Note: for details of orthogonal rotation, refer to Table 2-4, “Matrices and Orientation values for describing the orientation of a Component”. If a RotatePolicy value other than "NoRotate" is specified in FitPolicy , the actual rotation specified in Rotate MAY be modified accordingly. |
||
|
Defines the dimensions of the page cell. The lower left corner of the rectangle specified by the value of this Attribute establishes the coordinate system into which the page content is mapped. If not specified, TrimSize is calculated by subtracting the gutters from the LayoutPreparationParams /@ SurfaceContentsBox and dividing by the appropriate NumberUp value. |
||
|
Color ? |
||
|
Details how Device dependent marks are to be generated. Defaults to the value of DeviceMark in the parent LayoutPreparationParams . |
||
|
Details how page content is fit into the page cells. If the dimensions of the page contents vary, FitPolicy is applied to the contents of each cell individually. |
||
|
Element which describes how content is to be placed into the page cells. X and Y are specified in the coordinate system of the PageCell . |
7.2.112.2 Element: ImageShift
ImageShift Elements describe how the grid of page cells will be imaged onto media, when ImageShift is specified in the context of LayoutPreparationParams . When ImageShift is specified in the context of a PageCell , it specifies how content is imaged into the respective page cells.
|
|
Description for Figure 7-42
The following terms are used in Figure 7-42.
- reference grid in Figure 7-42 refers to the dashed red box around page cells of outermost Sheet, which indicates the size of the reference grid used in calculating grid placement relative to the SurfaceContentsBox origin using LayoutPreparationParams /@ ImageShift
- SCBx0 , SCBy0 , SFx , SFy , m , n and vg are used in the JDF below.
Figure 7-42 illustrates the JDF below. The JDF assumes that the dimensions of the RunList page's trim rectangle matches PageCell /@ TrimSize , whose dimensions are m by n (width and height) in the JDF example below. The Sheet with the widest creep gutter is on the top of the logical Sheet stack.
Example 7-36: LayoutPreparationParams: JDF for Figure 7-42
< JDF ID = "ID" Type = "ProcessGroup" xmlns = "http://www.CIP4.org/JDFSchema_1_1"
Status = "Waiting" JobPartID = "ID34" Version = "1.4" >
< LayoutPreparationParams Status = "Available" Class = "Parameter" ID = "LPP_2"
NumberUp = "2 2" PageDistributionScheme = "Saddle" FoldCatalog = "F8-7"
FoldCatalogOrientation = "Flip270" Sides = "TwoSidedFlipY"
StepRepeat = "1 1 1" SurfaceContentsBox = "0 0 612 792" BindingEdge = "Left"
VerticalCreep = "0" GutterMinimumLimit = "5 5" CreepValue = "0 -5"
Gutter = "20 20" FinishingOrder = "FoldCollect" FrontMarkList = "CutMark" >
<!-- Note: the value of some attributes in LayoutPreparationParams and
subElements relate to symbols in the above Figure:
SurfaceContentsBox = "SCBx0 SCBy0 SCBx1 SCBy1"
GutterMinimumLimit = "hml vml"
< PageCell TrimSize = "612 792" >
< ImageShift PositionX = "Spine" PositionY = "Center" />
< ImageShift PositionY = "Bottom" PositionX = "Left" ShiftFront = "20 20" />
< LayoutPreparationParamsLink Usage = "Input" rRef = "LPP_2" />
Description for Figure 7-43
The following terms are used in Figure 7-43.
- reference grid in Figure 7-43 refers to the dashed red box around page cells of innermost Sheet, which indicates the size of the reference grid used in calculating grid placement relative to the SurfaceContentsBox origin using LayoutPreparationParams /@ ImageShift
- SCBx0 , SCBy0 , SFx , SFy , m , n , vg and vig are used in the JDF below.
Figure 7-43 illustrates the JDF below. The JDF assumes that the dimensions of source content page rectangle matches PageCell /@ TrimSize , whose dimensions are m by n (width and height) in the JDF example below.
Example 7-37: LayoutPreparationParams: JDF for Figure 7-43
< JDF ID = "ID" Type = "ProcessGroup" xmlns = "http://www.CIP4.org/JDFSchema_1_1"
Status = "Waiting" JobPartID = "ID34" Version = "1.4" >
< LayoutPreparationParams Class = "Parameter" ID = "LPP_1" Status = "Available"
NumberUp = "4 1" PageDistributionScheme = "Saddle" FoldCatalog = "F4-1"
FoldCatalogOrientation = "Flip0" Sides = "TwoSidedFlipY" StepRepeat = "2 1 1"
SurfaceContentsBox = "0 0 612 792" VerticalCreep = "0 2"
ImplicitGutter = "0 30" ImplicitGutterMinimumLimit = "0 20" CreepValue = "0 5"
Gutter = "0 10" FinishingOrder = "GatherFold" FrontMarkList = "CutMark" >
<!-- Note: folding pattern F4-1 applies to each of the two 2x1
Note: step and repeat by two in X direction logically divides grid
Note: first (VC0) and third (VC2) vertical gutters are explicitly
creeping and the rest (~VC) are implicitly creeping
Note: Positive vertical creep value indicates initial gutter
Note: cut marks are located relative to largest page cell grid
Note: the value of some attributes in LayoutPreparationParams and
subElements relate to symbols in the above Figure:
SurfaceContentsBox = "SCBx0 SCBx1 SCBy0 SCBy1"
ImplicitGutterMinimumLimit = "0 vigl"
< PageCell TrimSize = "612 792" >
< ImageShift PositionX = "Spine" PositionY = "Bottom" />
< ImageShift PositionY = "Bottom" PositionX = "Left" ShiftFront = "20 20" />
< LayoutPreparationParamsLink Usage = "Input" rRef = "LPP_1" />
7.2.113 LayoutShift
|
Description of separation dependent transformations for a given point on the Layout . |
7.2.113.1 Element: ShiftPoint
|
CTM that MUST be applied to the Separation after all other transformations. |
||
|
Point that this ShiftPoint applies to. Note: the interpolation algorithm between ShiftPoint positions is implementation dependent. |
Example 7-38: LayoutShift
Example of absolute positions with @ Position
<JDF ID="ID" Type="ProcessGroup" xmlns="http://www.CIP4.org/JDFSchema_1_1"
Status="Waiting" JobPartID="ID34" Version="1.4">
<!-- LayoutShift SHOULD be partitioned: at least Side and Separation
< LayoutShift ID = "r000005" Class = "Parameter" Status = "Unavailable"
PartIDKeys = "Side Separation" >
<!-- LayoutShift SHOULD be partitioned: at least Side and Separation
<!-- Note that the interpolation algorithm between positions is
< LayoutShift Side = "Front" >
< LayoutShift Separation = "Cyan" >
< ShiftPoint CTM = "1 0 0 1 0 0" Position = "360 500" />
< ShiftPoint CTM = "1 0 0 1 0 2" Position = "1800 500" />
< ShiftPoint CTM = "1 0 0 1 1 0" Position = "360 1500" />
< ShiftPoint CTM = "1 0 0 1 1 2" Position = "1800 1500" />
< ShiftPoint CTM = "1 0 0 1 2 0" Position = "360 2500" />
< ShiftPoint CTM = "1 0 0 1 2 2" Position = "1800 2500" />
< ShiftPoint CTM = "1 0 0 1 3 0" Position = "360 3500" />
< ShiftPoint CTM = "1 0 0 1 3 2" Position = "1800 3500" />
< LayoutShift Separation = "Magenta" >
< ShiftPoint CTM = "1 0 0 1 1 1" Position = "360 500" />
< ShiftPoint CTM = "1 0 0 1 1 3" Position = "1800 500" />
< ShiftPoint CTM = "1 0 0 1 2 1" Position = "360 1500" />
< ShiftPoint CTM = "1 0 0 1 2 3" Position = "1800 1500" />
< ShiftPoint CTM = "1 0 0 1 3 1" Position = "360 2500" />
< ShiftPoint CTM = "1 0 0 1 3 3" Position = "1800 2500" />
< ShiftPoint CTM = "1 0 0 1 4 1" Position = "360 3500" />
< ShiftPoint CTM = "1 0 0 1 4 3" Position = "1800 3500" />
< LayoutShift Separation = "Yellow" >
< ShiftPoint CTM = "1 0 0 1 2 2" Position = "360 500" />
< ShiftPoint CTM = "1 0 0 1 2 4" Position = "1800 500" />
< ShiftPoint CTM = "1 0 0 1 3 2" Position = "360 1500" />
< ShiftPoint CTM = "1 0 0 1 3 4" Position = "1800 1500" />
< ShiftPoint CTM = "1 0 0 1 4 2" Position = "360 2500" />
< ShiftPoint CTM = "1 0 0 1 4 4" Position = "1800 2500" />
< ShiftPoint CTM = "1 0 0 1 5 2" Position = "360 3500" />
< ShiftPoint CTM = "1 0 0 1 5 4" Position = "1800 3500" />
< LayoutShift Separation = "Black" >
< ShiftPoint CTM = "1 0 0 1 3 3" Position = "360 500" />
< ShiftPoint CTM = "1 0 0 1 3 5" Position = "1800 500" />
< ShiftPoint CTM = "1 0 0 1 4 3" Position = "360 1500" />
< ShiftPoint CTM = "1 0 0 1 4 5" Position = "1800 1500" />
< ShiftPoint CTM = "1 0 0 1 5 3" Position = "360 2500" />
< ShiftPoint CTM = "1 0 0 1 5 5" Position = "1800 2500" />
< ShiftPoint CTM = "1 0 0 1 6 3" Position = "360 3500" />
< ShiftPoint CTM = "1 0 0 1 6 5" Position = "1800 3500" />
<LayoutShiftLink Usage="Input" rRef="r000005"/>
7.2.114 LongitudinalRibbonOperationParams
See Section P.4.8, “LongitudinalRibbonOperationParams” for details of this deprecated Resource.
7.2.115 ManualLaborParams
This Resource describes the parameters to qualify generic manual work within graphic arts production. Additional Comment Elements will generally be needed to describe the work in human readable form.
|
Type of manual labor that is performed. CreateCoatingForm - create a form to apply coatings during or after printing EditArt - Unspecific Art editing (for work on specific files LayoutElementProduction is to be used) ManageJob - General work on the Job. PhoneCallToCustomer - Phone calls to ask/inform the Customer. SeparateBlanks - Manual separation of blanks from a sheet after die cutting. New in JDF 1.4 Modification note: starting with JDF 1.3, the data type is changed from the erroneous NMTOKENS. |
7.2.116 Media
This Resource describes a physical element that represents a raw, unexposed printable surface such as Sheet, film or plate. Gloss , MediaColorName and Opacity Attributes provide media characteristics pertinent to color management.
Color / PrintConditionColor , Component , DieLayout , DigitalPrintingParams , EmbossingParams / Emboss , ExposedMedia , FeedingParams / Feeder , FeedingParams / CollatingItem , ImageSetterParams , InterpretingParams , Layout , LayoutPreparationParams , Media / MediaLayers , RasterReadingParams , ShapeDef , StrippingParams , Tile
Location, SheetName , Side , SignatureName , TileID , WebName
Bending , BoxPacking , Bundling , CaseMaking , ConventionalPrinting , ContactCopying , Cutting , DigitalPrinting , Embossing , Feeding , ImageSetting , Laminating , Varnishing , Wrapping
|
Identical to FrontCoatingDetail (see below), but applied to the back surface of the media. |
||
|
Identical to FrontCoatings (see below), but applied to the back surface of the media. |
||
|
Gloss of the back surface of the media in gloss units as defined by [ISO8254-1:1999] . When not known, BackGlossValue defaults to the value of FrontGlossValue . |
||
|
Reflectance percentage of diffuse blue reflectance as defined by [ISO2470:1999] . The reflectance is reported per [ISO2470:1999] as the diffuse blue reflectance factor of the paper or board in percent to the nearest 0.5% reflectance factor. If one value is specified, Brightness applies to the front and back. If two values are specified the first value applies to the front and the second applies to the back. See also CIEWhiteness . |
||
|
Average CIE tint value. Average CIE tint is calculated according to equations given in [TAPPI T560] . |
||
|
Average CIE whiteness value. Average CIE whiteness is calculated according to equations given in [TAPPI T560] . |
||
|
Link to a definition of the color specifics. The value of ColorName color should match the Name Attribute of a Color defined in a ColorPool Resource that is linked to the Process using this Media Resource. Deprecation note: starting with JDF 1.2, use MediaColorName and MediaColorNameDetails . |
||
|
The X and Y dimensions of the chosen medium, measured in points. Dimension specifies the outer bounding box of the Media . The X, Y values of Dimension establishes the user coordinate system into which content is mapped, (i.e., the origin is in the lower left corner of the rectangle defined by 0 0 X Y.) In case of Roll media, the X coordinate specifies the reel width and the Y coordinate specifies the length of the Web in points. If a Dimension coordinate is unknown, the value must be "0" . If not specified, the dimension is unknown. If either or both X or Y = "0" (i.e., unknown), the default orientation is assumed to be portrait, (i.e., Y > X). Values include those from: Table G-1, “Media Sizes”. New in JDF 1.4 Modification note: starting with JDF 1.4, the description states that Dimension specifies the outer bounding box of the Media and new values are specified. |
||
|
Single, capital letter that specifies the Flute type of corrugated media. Although the classification of flutes using a letter code “A”, “B”, etc., are used very frequently e.g., in the specification of the order for a box, there seems to be no agreement on the exact numerical specification of those categories. Slightly varying numbers for flute size and frequency can be found between regions (European versus US) and between vendors. |
||
|
LongEdge - Along the longer axis as defined by Dimension . ShortEdge - Along the shorter axis as defined by Dimension . XDirection - Along the X-axis of the Media coordinate system YDirection - Along the Y-axis of the Media coordinate system |
||
|
Describes (beyond FrontCoatings ) the coating to the front surface of the media and possibly the technology used to apply the coating. |
||
|
What preprocess coating has been applied to the front surface of the media. Coated - A coating of a system-specified type. New in JDF 1.2 InkJet - A coating intended for use with inkjet technology. Deprecation note: use PrintingTechnology = "InkJet" New in JDF 1.2 Deprecated in JDF 1.4 Polymer - Coating for a photo polymer process New in JDF 1.3 |
||
|
Gloss of the front side of the of the media in gloss units as defined by [ISO8254-1:1999] . Refer also to [TAPPI T480] for examples of gloss calculation. |
||
|
The Grade of the media on a scale of 1 through 5. The Grade is ignored if MediaType is not "Paper" . Grade of paper material is defined in accordance with the paper “types” set forth in [ISO12647-2:2004] . Note: [ISO12647-2:2004] paper type Attribute Values do NOT align with U.S. GRACOL paper grade Attribute Values, (e.g., [ISO12647-2:2004] type 1 does not equal U.S. GRACOL grade 1). |
||
|
Direction of the grain in the coordinate system defined by Dimension . LongEdge - Along the longer axis as defined by Dimension . ShortEdge - Along the shorter axis as defined by Dimension . XDirection - Along the X-axis of the Media coordinate system. New in JDF 1.3 YDirection - Along the Y-axis of the Media coordinate system. New in JDF 1.3 |
||
|
The number of holes that are to be punched in the media (either pre- or post-punched). In JDF/1.1, use HoleType , Hole or HoleLine , which includes the number of holes. |
||
|
Predefined hole pattern. Multiple hole patterns are allowed, (e.g., 3-hole ring binding and 4-hole ring binding holes on one piece of media). For details of the hole types, refer to Appendix L, “JDF/CIP4 Hole Pattern Catalog” . Explicit - Holes are defined in a HoleList . Values are from: Appendix L, “JDF/CIP4 Hole Pattern Catalog” . |
||
|
Specifies the inner diameter of the core of a Roll, in points. See also OuterCoreDiameter and RollDiameter . |
||
|
The inside loss of corrugated board material in microns [m]. Note: InsideLoss + OutsideGain need not be exactly equal to thickness. |
||
|
LabColorValue is the CIELAB color value of the media, computed as specified in [TAPPI T527] . |
||
|
A name for the color. Allowed values are defined in Section A.3.3.3, “NamedColor”. If more specific, specialized or site-defined media color names are needed, use MediaColorNameDetails . |
||
|
A more specific, specialized or site-defined name for the media color. If MediaColorNameDetails is supplied, MediaColorName SHOULD also be supplied. |
||
|
Named quality description of the media. For folding carton quality, multiple named quality description systems are in use. E.g. GC1, SBB, etc. For an overview see |
||
|
When the input media is grouped in sets, identifies the number of pieces of media in each set. For example, if the MediaTypeDetails is "PreCutTabs" , a MediaSetCount of "5" would indicate that each set includes five tab Sheets. |
||
|
Describes the medium being employed. CorrugatedBoard New in JDF 1.3 Disc - CD or DVD disc to be printed on. EndBoard - end board used in the Bundling Process. GravureCylinder - gravure cylinder. New in JDF 1.3 ImagingCylinder - reusable direct imaging cylinder in a press. New in JDF 1.3 MountingTape - for flexo plate mounting tape. New in JDF 1.4 Other - not one of the defined values. Screen - used for Screen Printing. New in JDF 1.4 |
||
|
Additional details of the chosen medium. Constraint: If MediaTypeDetails is specified, MediaType must be specified. Values include those from: Table 7-268, “MediaTypeDetails Attribute Values”. |
||
|
Describes the format of the media as it is delivered to the Device. Continuous - Continuously connected Sheets which can be fan folded. New in JDF 1.2 |
||
|
The opacity of the media. See OpacityLevel to specify the degree of opacity for any of these values. Opaque - The media is opaque. With two-sided printing the printing on the other side does not show through under normal incident light. Translucent - The media is translucent to a system specified amount. For example, translucent media can be used for back lit viewing. New in JDF 1.2 |
||
|
Normalized TAPPI opacity, (Cn), as defined and computed in [ISO2471:1998] . Refer also to [TAPPI T519] for calculation examples. |
||
|
Specifies the outer diameter of the core of a Roll, in points. See also InnerCoreDiameter and RollDiameter . |
||
|
The outside gain of corrugated board material in microns [m]. |
||
|
Exposure technology of the plates. FlexoAnalogSolvent New in JDF 1.4 FlexoAnalogThermal New in JDF 1.4 FlexoDigitalSolvent New in JDF 1.4 FlexoDigitalThermal New in JDF 1.4 FlexoDirectEngraving New in JDF 1.4 InkJet - Exposure with inkjet technology. Note that FrontCoatings = "Inkjet" specifies inkjet specific coating of paper or transparency Media, not of plates. |
||
|
Describes the printing technology that the media or coatings on the media are intended for or optimized for. |
||
|
If "true" , recycled media is requested. If not specified, the Media might have recycled content. In JDF 1.2 and beyond, use RecycledPercentage . |
||
|
The percentage, between 0 and 100, of recycled material that the media is to contain. |
||
|
The thickness of the relief, measured in microns [m]. The floor thickness can be calculated as ( Thickness - ReliefThickness ). See Figure 7-45. |
||
|
Specifies diameter of a Roll, in points. See also InnerCoreDiameter and OuterCoreDiameter . |
||
|
Specifies the ratio of the media linear dimension after shrinking to prior shrinking. The X Value specifies index in the major shrink axis, whereas the Y Value specifies the index in the minor shrink axis. Used to describe shrink wrap media. |
||
|
The type of interlock (or notch) to use for a flexo sleeve. Type01 - see Figure 7-46. Type20 - see Figure 7-46. |
||
|
Strings describing the available stock. StockType defines the base size when calculating North American or Japanese paper weights. See Appendix F, “North American and Japanese Media Weight Explained” . New in JDF 1.4 Values with Kanji names support Japanese media. Offset - This includes book stock. Aatoposutoshi - アートポスト紙 (“art-post paper”) is cover stock coated on one side. New in JDF 1.4 Aatoshi -アート紙 (“art paper”) is machine coated paper, available in top quality and medium quality ( Joushitsu and Chuushitsu ). New in JDF 1.4 Chuushitsushi - 中質紙(“medium-quality paper”) contains a minimum of 70% chemical pulp. New in JDF 1.4 Joushitsushi - 上質紙 (“top-quality paper”) contains 100% chemical pulp. New in JDF 1.4 Mashinkootoshi -マシンコート紙 (“machine coated paper”), also called Kootoshi (コート紙), is machine coated paper given only a thin coat of clay. New in JDF 1.4 |
||
|
The intended texture of the media. Antique - Rougher than vellum surface. Calendared - Extra smooth or polished, uncoated paper. Linen - Texture of coarse woven cloth. Uncalendared - Rough, unpolished and uncoated papers. New in JDF 1.2 |
||
|
The thickness of the chosen medium, measured in microns [m]. |
||
|
A human-readable description of the type of media. The value can be used by an operator to select the correct media to load. The semantics of the values will be site-specific. Deprecation note: starting with JDF 1.1, UserMediaType has been merged into MediaTypeDetails . |
||
|
Weight of the chosen medium, measured in grams per square meter [g/m2] . See Appendix F, “North American and Japanese Media Weight Explained” for details on converting North American paper weights to g /m2. |
||
|
Color ? |
A Color Resource that provides the color of the chosen medium. |
|
|
Detailed description of the measurement conditions for color measurements used to measure LabColorValue . |
||
|
HoleList ? |
Explicit list of holes. HoleList MUST be specified if HoleType = "Explicit" . |
|
|
Subelement describing the layer structure of media such as corrugated or self adhesive materials. |
||
|
Specifies the dimensions of the tabs when MediaTypeDetails = "TabStock" , "PreCutTabs" or "FullCutTabs" . Note: see BindingIntent / Tabs (Table 7-31, “Tabs Element”) (rather than MediaIntent ) for how tabbed media is specified in Product Intent. |
-- Attribute: MediaTypeDetails
|
|
|
7.2.116.1 Element: MediaLayers
MediaLayers contains an ordered list of Subelements. Each Subelement describes an individual layer of a layered Media Resource. The first layer in MediaLayers is the front layer of the Media until the last layer, which defines the back.
|
GlueLine * |
GlueLine Resource describing a glue layer of a layered Media Resource. Each GlueLine Resource must have GlueLine / @AreaGlue = "true" . |
|
|
Media * |
Media Resources describing a layer of a layered Media Resources. |
7.2.116.2 Element: TabDimensions
Specifies the size and placement of tabs in a bank and in a set of tab stock.
|
Indicates which edge of the media has tabs. Sets the coordinate system for TabOffset , TabExtensionDistance , and TabWidth . |
||
|
The positive distance in points that the tab extends beyond the body of the other media. Note: same as BindingIntent / Tabs /@ TabExtensionDistance . Note: This value is always included in the value of the overall extent of the Media defined by Media /@ Dimension . See Figure 7-48, “Diagram of a Single Bank of Tabs”. |
||
|
Specifies the magnitude of the distance in points from the two corners to the edge of the first “tab pitch” point of the first tab in the bank along the TabEdge . This distance is the same on both ends of the bank of tabs. See Figure 7-48, “Diagram of a Single Bank of Tabs”. |
||
|
Specifies the number of equal-sized tabs in a single bank if all positions were filled. Note: banks can have tabs only in some of the possible positions. Note: same as BindingIntent / Tabs /@ TabsPerBank . Media /@ MediaSetCount specifies the number of tabs per set. A set can consist of one or more banks. If Media /@ MediaSetCount is not an even multiple of TabsPerBank , the last bank in each set is partially filled. |
||
|
Collation order of media provided in sets. Applicable to sets of pre-cut tabs. See Figure 7-47, “TabSetCollationOrder Attribute Values”. |
||
|
The width along the TabEdge of each tab as measured along the mid-line of the tab. Each tab is centered within a space called the “tab pitch”. See Figure 7-48, “Diagram of a Single Bank of Tabs”. |
|
|
7.2.116.3 More about Media
7.2.116.3.1 Inside Loss and Outside Gain
Inside loss and outside gain: dimensional values used in the mechanical design phase of a box. (Note: IL + OG is not exactly equal to thickness. Thickness is most often referred to as caliper.)
|
7.2.116.3.2 Corrugated Media:
Corrugated material consists of multiple Sheets of paper (called liners) with fluted material in between. For background information on Corrugated Media, see http://cpc.corrugated.org/Basics . Corrugated media comes in different variants.
Example 7-39: Media: Corrugated
<JDF ID="ID" Type="ProcessGroup" xmlns="http://www.CIP4.org/JDFSchema_1_1"
Status="Waiting" JobPartID="ID34" Version="1.4">
< Media Class = "Consumable" ID = "M123456" ProductID = "B190Y180D1050x120"
Status = "Available" DescriptiveName = "B Flute 190Y 180D 1050x1210"
Dimension = "1050.0 120.0" MediaType = "CorrugatedBoard"
MediaTypeDetails = "SingleWall" MediaUnit = "Sheet" Thickness = "2382.0"
InsideLoss = "1000.0" OutsideGain = "1380.0" Weight = "600" >
< Media DescriptiveName = "190gsm clay coated" MediaType = "Paper"
Weight = "190" FrontCoatings = "Coated" />
< Media DescriptiveName = "Flute" MediaType = "Paper" Weight = "180"
FluteDirection = "ShortEdge" Flute = "B" MediaTypeDetails = "Flute" />
< Media DescriptiveName = "180gsm white top" MediaType = "Paper"
<MediaLink Usage="Input" rRef="M123456"/>
7.2.116.3.3 Self adhesive Media
Self adhesive media is described as MediaLayers Elements with nested Media and GlueLine Elements.
Example 7-40: Media: Self Adhesive
<JDF ID="ID" Type="ProcessGroup" xmlns="http://www.CIP4.org/JDFSchema_1_1"
Status="Waiting" JobPartID="ID34" Version="1.4">
< Media Class = "Consumable" ID = "M123456" ProductID = "7890123" Status = "Available"
DescriptiveName = "40# Fasson coated label stock" Dimension = "1134.0 0"
MediaType = "SelfAdhesive" MediaUnit = "Roll" Thickness = "1000.0"
< Media DescriptiveName = "Antique Cream Smooth WS IL" MediaType = "Paper"
< GlueLine DescriptiveName = "Permanent 91A" AreaGlue = "true"
GlueType = "Hotmelt" GlueBrand = "Uhu" />
< Media DescriptiveName = "Blue Glassine 50" MediaType = "Paper" Weight = "50" />
<MediaLink Usage="Input" rRef="M123456"/>
7.2.116.3.4 Flexo Plate Media
A sample of a flexo plate with dimensions of 900 mm x 1200 mm, a base of 177 microns and a total thickness of 1143 microns.
A raw plate can contain several separations from multiple jobs. The real printing dimensions can only be determined when all elements of the mounting process are known: circumference of the sleeve on which the flat plate will be mounted, thickness of the mounting tape, thickness of base and thickness of the photopolymer.
Example 7-41: Media: Flat Plate
<JDF ID="ID" Type="ProcessGroup" xmlns="http://www.CIP4.org/JDFSchema_1_1"
Status="Waiting" JobPartID="ID34" Version="1.4">
< Media Class = "Consumable" ID = "M123456" ProductID = "FlexoPlate"
Status = "Available" DescriptiveName = "" Dimension = "2551.181 3401.574"
MediaType = "Plate" PlateTechnology = "FlexoDigitalThermal"
Manufacturer = "PlateManufactererA" Brand = "BrandB" BatchID = "Batch 12345"
Thickness = "1143" ReliefThickness = "500" >
<!-- MediaLayers contains 2 items: the base layer and the
---- photopolymer layer of the flexo plate
< Media DescriptiveName = "Base" MediaType = "Plate"
MediaTypeDetails = "FlexoPlateBase" Thickness = "177" />
< Media DescriptiveName = "Photopolymer Layer" MediaType = "Plate"
MediaTypeDetails = "FlexoPlatePhotopolymer" Thickness = "966" />
Example 7-42: Media: Flexo Sleeve
<JDF ID="ID" Type="ProcessGroup" xmlns="http://www.CIP4.org/JDFSchema_1_1"
Status="Waiting" JobPartID="ID34" Version="1.4">
< Media Class = "Consumable" ID= "M123456" ProductID = "FlexoSleeve"
DescriptiveName = "Sleeve" Dimension = "1417.32 750.0" MediaType = "Sleeve"
PlateTechnology = "FlexoDigitalSolvent" Manufacturer = "PlateManufactererB"
Brand = "BrandB" BatchID = "Batch 6789" Thickness = "2810"
<!-- MediaLayers contains 2 items: the base layer and the
---- photopolymer layer of the flexo plate
< Media DescriptiveName = "Base" MediaType = "Plate"
MediaTypeDetails = "FlexoPlateBase" Thickness = "1249" />
< Media DescriptiveName = "Photopolymer Layer" MediaType = "Plate"
MediaTypeDetails = "FlexoPhotopolymer" Thickness = "1570" />
<MediaLink Usage="Input" rRef="M123456"/>
7.2.117 MediaSource
See Section P.4.9, “MediaSource” for details of this deprecated Resource.
7.2.118 MiscConsumable
The MiscConsumable Resource is intended for cost accounting, inventory control and availability scheduling of supplies used in the production workflow where a more detailed parameterization of the Resource is not necessary. MiscConsumable is limited to modeling consumables not already more specifically defined in JDF ( Ink , Media , Pallet , RegisterRibbon , Strap or UsageCounter ).
MiscConsumable Resources may appear as inputs to any JDF Process. The default Unit for Amounts of MiscConsumable is Countable Objects.
Certain types of MiscConsumable Elements such as MiscConsumable [@ ConsumableType = "WasteContainer" ] are typically “consumed” by being filled. The sense of the Amount Attribute for such Resources shall be the quantity of unused or empty waste containers that are available. If Unit is a volume, distance or weight instead of Countable Objects, such Amount will still represent the remaining unused capacity of the waste container.
|
Identifies the type of MiscConsumable (machine-readable). A human-readable (possibly localized) description of the consumable should also be supplied in DescriptiveName . |
7.2.119 MISDetails
MISDetails is a container for MIS related information. It is referenced by Audit Elements and JMF Messages.
PhaseTime , ResourceAudit , ResourceCmdParams , ResourceInfo , ResourcePullParams , JobPhase , NodeInfo
|
Complexity of the task specified by this JDF Node in a range from 0.0 to 1.0. Note: the interpretation of values is implementation dependant. 0.0 - The job is simple and therefore reduced setup and waste or higher speeds are possible. 0.5 - The job is of standard complexity and therefore standard setup and waste or normal speeds are possible. 1.0 - The job is complex and therefore more setup and waste or lower speeds are possible. |
||
|
Whether or not this MISDetails is chargeable to the customer or not. |
||
|
DeviceOperationMode shows the operation mode that the Device is in. It is used to show if the production of a Device is aimed at producing good products or not. The latter case applies when a Device is used to produce a Job for testing, calibration, etc., without the intention to produce good output. Productive - The Device is used to produce good product. Any times recorded in this mode are to be allocated against the Job. NonProductive - The Device is used without the intention to produce good product. Any times recorded in this mode are not to be allocated against the Job. Maintenance -The Device is used without the intention to produce good product, e.g., to perform (preventive) maintenance. |
||
|
Definition of the work type for this MISDetails , (i.e., whether or not this MISDetails relates to originally planned work, an alteration or rework). Original - Standard work that was originally planned for the Job. Alteration - Work done to accommodate change made to the Job at the request of the customer. Rework - Work done due to unforeseen problem with original work (bad plate, Resource damaged, etc.) |
||
|
Definition of the details of the work type for this MISDetails , (i.e., why the work was done). CustomerRequest - The customer requested change(s) requiring the work. EquipmentMalfunction - Equipment used to produce the Resource malfunctioned; Resource needs to be created again. InternalChange - Change was made for production efficiency or other internal reason. ResourceDamaged - A Resource needs to be created again to account for a damaged Resource (damaged plate, etc.). UserError - Incorrect operation of equipment or incorrect creation of Resource requires creating the Resource again. |
7.2.120 NodeInfo
The NodeInfo Resource contains information about planned scheduling and message routing. It allows MIS to plan, schedule and invoice Jobs or Job Parts. Prior to JDF 1.3, NodeInfo was a direct Subelement of the JDF Node and not a Resource.
Modification note: starting with JDF 1.3, NodeInfo is a Resource that MUST be linked (via NodeInfoLink ) like any other Resource; there is no “inheritance”. However, a Node MAY link to the same NodeInfo Resource as its parent
Note: the NORMATIVE NodeInfo is specified by a linked Resource. An Informative NodeInfo MAY be retrieved by searching the NodeInfo of parent Nodes or Ancestor Elements.
|
Description of the severity of a missed deadline. Unknown - Consequences of missing the deadline are not known. Deprecated in JDF 1.2 Trivial - Missing the deadline has minor or no consequences. Penalty - Missing the deadline incurs a penalty. JobCancelled - The Job is cancelled if the deadline is missed. |
||
|
A pair of numbers (as integers) indicating the version of the IPP protocol to use when communicating to IPP Devices. The X value is the major version number. |
||
|
The scheduling priority for the Node where 100 is the highest and 0 is the lowest. Amongst the Nodes that can be processed in the JDF Instance, all higher priority Nodes are to be processed before any lower priority ones. If one or more of the deadline oriented Attributes (e.g., FirstStart or LastEnd ) is specified, such attribute(s) MUST be honored before considering JobPriority . The priority from JMF ( QueueSubmissionParams /@ Priority or QueueEntryPriParams /@ Priority ) takes precedence over NodeInfo /@ JobPriority . Modification note: starting with JDF 1.4, scheduling priority in the first paragraph is described in terms of the Node rather than the job |
||
|
Latest date and time at which the Process is to end. This is the deadline to which DueLevel refers. |
||
|
Language selected for communicating Attributes. If not specified, the operating system language is assumed. |
||
|
Identifies the status of an individual part of the Node. Default value is from: JDF /@ Status . Values are from: JDF /@ Status ( Table 3-5, “JDF Node”). |
||
|
Description of the status that provides details beyond the enumerative values given by NodeStatus . Default value is from: JDF /@ StatusDetails Values include those from: Section C.1, “StatusDetails Supported Strings” . |
||
|
If MergeTarget = true and this Node has been spawned, it must be merged with its direct ancestor by the Controller that executes this Node. The path of the ancestor is specified in the last Ancestor Element located in the AncestorPool of this Node. It is an error to specify both MergeTarget and TargetRoute in one Node. Note: MergeTarget has been deprecated in JDF 1.1 because avoiding concurrent access to the ancestor Node is ill defined and cannot be implemented in an open system without proprietary locking mechanisms. |
||
|
The URL of the Controller or Device that is to execute this Node. If Route is not specified, the routing Controller must determine a potential target Controller or Device independently. For details, see Section 4.2, “Process Routing”. Note that the receiving Device must not use Route to determine whether to execute the Node. Rather a Device must use a Device Input Resource (if specified) to determine whether to execute the Node. |
||
|
Array of ID s of any Elements that are specified as ResourceRef Elements. In version 1.1, rRefs contained the IDREF of an Employee . In JDF 1.2 and beyond, it is up to the implementation to maintain references. |
||
|
The URL where the JDF is to be sent after completion. If TargetRoute is not specified, it defaults to the input Route Attribute of the subsequent Node in the Process chain. If this is also not known (e.g., because the Node is spawned), the JDF Node MUST be sent to the processor default output URL. If TargetRoute specifies a file-schemed URL, it MUST be the exact file name and NOT just the directory of the resulting JDF. JMF / QueueSubmissionParams /@ ReturnURL takes precedence over NodeInfo /@ TargetRoute of the JDF that is processed. |
||
|
Estimated total duration of the Process, including setup and cleanup. |
||
|
Container for business related information. It is expected that JDF will be utilized in conjunction with other e -commerce standards, and this container is provided to store the e -commerce information within JDF in case a workflow with JDF as the root level document is desired. When JDF is used as part of an e -commerce solution such as PrintTalk, the information given in the envelope document overrides the information in BusinessInfo . |
||
|
ID of an individual work step, e.g. a Press Run. If NodeInfo is not Partitioned, or all Partitions are executed simultaneously, WorkStepID corresponds to JobPartID . |
||
|
Employee ? |
The internal administrator or supervisor that is responsible for the product or Process defined in this Node. |
|
|
JMF * |
Represents JMF Query Messages that set up a persistent channel, as described in Section 5.4.3, “Persistent Channels”. These Message Elements define the receiver that is designated to track Jobs via JMF Messages. These Message Elements should be honored by any JMF-capable Controller or Device that executes this Node. When these Messages are honored, a persistent communication channel is established that allows Devices to transmit, (e.g., the status of the Job as JMF Signal Messages). The JMF specified in this NodeInfo MUST be restricted in scope to the containing JDF Element. Typically this will be achieved by explicitly stating JobID in the appropriate QueryTypeObj . |
|
|
Definition how the costs for the execution of this Node are to be charged. |
||
|
Defines the set of Notification Elements that are to be logged in the AuditPool . This provides a logging method for Devices that do no not support JMF messaging. For details of the NotificationFilter Element, see Section 5.8.1, “Events”. |
7.2.121 NumberingParams
This Resource describes the parameters of stamping or applying variable marks in order to produce unique components, (e.g., lottery notes, currency). One NumberingParams Element must be defined per numbering machine.
7.2.121.1 Element: NumberingParam
7.2.122 ObjectResolution
ObjectResolution defines a resolution depending on SourceObjects data types.
InterpretingParams , RenderingParams , TrappingDetails
|
Indicates the anti-aliasing algorithm that the Device must apply to the rendered output images. An anti-aliasing algorithm causes lines and curves to appear smooth which would otherwise have a jagged appearance, especially at lower resolutions such as 300 dpi and lower. AntiAlias - Anti-aliasing must be applied. The algorithm is system specified. |
||
|
Tags associated with individual objects that this ObjectResolution MUST be applied to. Each tag specified in ObjectTags is logically anded with the object type(s) specified by SourceObjects , enabling first qualification by object type (such as image), and then tags associated with those objects. The values of ObjectTags depends on the PDL that the ObjectResolution is applied to. |
||
|
Identifies the class(es) of incoming graphical objects to render at the specified resolution. ImagePhotographic - Contone images. ImageScreenShot - Images largely comprised of rasterized vector art. LineArt - Vector objects other than text. |
7.2.123 OrderingParams
Attributes of the Ordering Process, which results in an acquisition.
|
OrderingParams require a Comment Element that contains a human-readable description of what to order. |
||
|
Company ? |
Address and further information of the Company responsible for this order. Replaced with Contact / Company in JDF 1.1. |
|
|
Contact * |
Address and further information of the Contact responsible for this order. |
7.2.124 PackingParams
The PackingParams Resource has been deprecated in JDF 1.1 and beyond. It is replaced by the individual Resources used by the Processes defined in Section 6.7.5, “Packaging Processes”. See Section P.4.10, “PackingParams” for details of this deprecated Resource.
7.2.125 PageAssignParams
This Resource is an empty container for future extensions
7.2.126 PageList
PageList defines the additional metadata of individual finished pages such as pagination details. PageList references the finished page regardless of the page’s position in a PDL file or RunList .
Assembly , Component , ExposedMedia , LayoutElement , RunList
|
ID of the Assembly or AssemblySection that this finished page belongs to. |
||
|
IDs of the Assembly Elements, AssemblySection Elements or StrippingParams [@ BinderySignatureName ] that the finished pages specified by this PageList belong to. |
||
|
If "true" , the PageList has no content marks and is blank. Note that in JDF 1.2, the description erroneously stated that IsBlank = "false" specifies a blank page. |
||
|
If "true" , the file is a PDL file and can be printed. Possible files types include PCL, PDF or PostScript files. Application files such as MS Word have IsPrintable = "false" . |
||
|
Prefix of the identification of the Reader Page as it is displayed on the finished page. For instance "C-" , if the Reader Pages are labeled "C-1" , "C-2" , etc. |
||
|
Suffix of the identification of the Reader Page as it is displayed on the finished page. For instance "-a" , if the pages are labeled "C-1-a" , "C-2-a" , etc. |
||
|
A rectangle that describes the bleed area of the page to be included. This rectangle is expressed in the source coordinate system of the object. If not specified, use defined bleed box of element (or no bleed box if element does not supply a bleed box). |
||
|
A rectangle that defines the region of the finished page to be included. This rectangle is expressed in the source coordinate system of the object. If not specified, use defined clip box of element (or no clip box if element does not supply a clip box.) |
||
|
A rectangle that describes the intended trimmed size of the finished page to be included. This rectangle is expressed in the source coordinate system of the object. If not specified, use defined trim box of element (or no trim box if element does not supply a trim box.) |
||
|
Template is "false" when this page is self-contained. This Attribute is "true" if the PageList represents a template that must be completed with information from a database. |
||
|
Assembly ? |
Assembly that is referred to by AssemblyIDs or contains the AssemblySection that is referred to by AssemblyIDs. |
|
|
List of ContentData Elements that describe individual pieces of content on the pages. |
||
|
PageData * |
Details of the individual finished page. The PageData Elements are referred to by the values of PageData /@ PageIndex (if present), or otherwise, their index in the PageList . In the latter case, the PageData Elements should , therefore, not be removed or inserted in a position other than the end of the list Modification note: see the Modification note in the section on the PageData Element below. |
|
|
List of separation names defined in the PageList . |
7.2.126.1 Element: PageData
PageData defines the additional metadata of individual finished pages or sets of finished pages with common properties, such as pagination details.
If PageIndex is not present in PageData Elements, PageData Elements are referred to by index of the PageData in the PageList . If PageIndex is present, it explicitly specifies the indices within the PageList . Either all or no PageData Elements in a PageList MUST have PageIndex . If a Page is not represented by a PageData , the Attributes of the PageList itself apply.
Modification note: starting with JDF 1.4, PageData /@ PageIndex is added It allows PageData to describe multiple finished pages and to explicitly specify the index of a PageData Element within a PageList . The explicit index allows a PageList to contain a PageData for a particular index (e.g. 100) without the need for PageData Elements for all indices that are lower (e.g. 0 to 99). Without PageIndex , the position of PageData within PageList implicitly specifies its index.
If the PageList is Partitioned, the index refers to PageData Elements in the respective leaves of the Partitioned PageList . The index restarts at 0 with each Partitioned leaf.
|
ID of the Assembly or AssemblySection that this finished page belongs to. Default value is from: PageList /@ AssemblyID |
||
|
IDs of the Assembly Elements, AssemblySection Elements or StrippingParams [@ BinderySignatureName ] that this finished page belongs to. Default value is from: PageList /@ AssemblyIDs . |
||
|
Identification of the Resource, (e.g., in a catalog environment). Default value is from: PageList /@ CatalogID . |
||
|
Additional details of a Resource in a catalog environment. Default value is from: PageList /@ CatalogDetails . |
||
|
Page indices in the PageList of the file pages forming a content page that flows over multiple finished pages, (e.g., foldout, centerfold). The list does not include the index of this PageData . Default behavior: PageData does not describe a part of a foldout. |
||
|
If "true" , the file has bleeds. Default value is from: PageList /@ HasBleeds . |
||
|
If "true" , the PageData has no content marks and is blank. Note that in JDF 1.2 the description erroneously stated that IsBlank = "false" specifies a blank page. Default value is from: PageList /@ IsBlank . |
||
|
If "true" , the file is a PDL file and can be printed. Possible files types include PCL, PDF or PostScript files. Application files such as MS Word have IsPrintable = "false" . Default value is from: PageList /@ IsPrintable . |
||
|
If "true" , the file has been trapped. Default value is from: PageList /@ IsTrapped . |
||
|
ID of the Job that this finished page belongs to. Default value is from: PageList /@ JobID . |
||
|
Defines the format of the page in a production workflow. Broadsheet - One single page that will be mounted on a broadsheet plate (one page goes on one (broadsheet) plate). Tabloid - One single page that will be paired with a second tabloid page. Later, the page pair will be mounted on a broadsheet plate. Newspaper4up - Four pages will be mounted on one plate. |
||
|
List of pages the PageData Element represents. A Page number MUST NOT appear more than once in the PageList . |
||
|
Complete identification of the finished page including PageLabelPrefix and PageLabelSuffix as it is displayed on the finished page, For instance "1" , "iv" or "C-1" . Note that this might be different from the position of the page in the finished document. |
||
|
Prefix of the identification of the Reader Page as it is displayed on the finished page. For instance "C-" , if the Reader Pages are labeled "C-1" , "C-2" , etc. Default value is from: PageList /@ PageLabelPrefix |
||
|
Suffix of the identification of the Reader Page as it is displayed on the finished page. For instance "-a" , if the pages are labeled "C-1-a" , "C-2-a" , etc. Default value is from: PageList /@ PageLabelSuffix |
||
|
Status of a single PageData Element. Values include those from: Table C-20, “MessageEvents and MilestoneType Values” . |
||
|
An ID of the page as defined in the MIS system. Default value is from: PageList /@ ProductID |
||
|
A rectangle that describes the bleed area of the page to be included. This rectangle is expressed in the source coordinate system of the object. Default value is from: PageList /@ SourceBleedBox |
||
|
A rectangle that defines the region of the finished page to be included. This rectangle is expressed in the source coordinate system of the object. Default value is from: PageList /@ SourceClipBox |
||
|
A rectangle that describes the intended trimmed size of the finished page to be included. This rectangle is expressed in the source coordinate system of the object. Default value is from: PageList /@ SourceTrimBox . |
||
|
Template is "false" when this page is self-contained. This Attribute is "true" if the PageList represents a template that must be completed with information from a database. Default value is from: PageList /@ Template |
||
|
Color details of the PageData Element. Default value is from: PageList / ElementColorParams |
||
|
Specification of the image compression properties. Default value is from: PageList / ImageCompressionParams |
||
|
Describes an individual element on a page. This might be a part of an image, text, advertisement, editorial, etc. |
||
|
Specification of the screening properties. Default value is from: PageList / ScreeningParams |
||
|
List of separation names defined in the Element. Default value is from: PageList / SeparationSpec |
7.2.126.2 Element: PageElement
PageElement defines the additional metadata of individual Elements within a page.
|
ID of the ContentData Elements in the referenced ContentList . ContentData Elements provide Metadata related to this PageData . ContentDataRefs MUST NOT be specified if no ContentList is specified in the grand-parent PageList Element. |
||
|
Index into a ContentList / ContentData Element. If neither ContentListIndex nor PageElement are specified, this PageElement is a reservation. Deprecation note: starting with JDF 1.4, use ContentDataRefs . |
||
|
List of Pages that this PageElement traverses, e.g., fold out pages or multi-page ads. |
||
|
Type of content that is placed in this PageElement . Values include those from: ContentList / ContentData /@ ContentType |
||
|
Position of the PageElement in the coordinate system of the parent PageElement or PageList . |
||
|
Further sub-page Elements that comprise this PageElement . |
7.2.127 Pallet
A Pallet represents the pallet used in packing goods.
7.2.128 PalletizingParams
PalletizingParams defines the details of Palletizing . Details of the actual pallet used for Palletizing can be found in the Pallet Resource that is also an input of the Palletizing Process.
|
Ordered number of input components in a layer. The first number is the first layer on the bottom. If there are more layers than entries in the list, counting restarts at the first entry. |
||
|
Name of the palletizing pattern. Used to store a predefined pattern that defines the layers and positioning of individual component on the pallet. |
||
|
Bundle ? |
Describes additional properties, such as the number of individual products, and describes the list of the individual products on the pallet |
7.2.129 PDFToPSConversionParams
This Resource specifies a set of configurable options that can be used by Processes that generate PostScript files. Prior to JDF 1.3, PDFToPSConversionParams was used only for converting PDF files to PostScript. The name “ PDFToPSConversionParams ” was retained for backwards compatibility, although most parameters apply to PDF conversion from any source format.
Some descriptions below mention Attributes or structures in specific source formats, such as PDF. Appropriate equivalent actions should be taken when converting from other source formats that have equivalent Attributes or structures. A small number of parameters apply only to PDF sources.
Font controls are applied in the following order:
- 1 IncludeBaseFonts
- 2 IncludeEmbeddedFonts
- 3 IncludeType1Fonts
- 4 IncludeType3Fonts
- 5 IncludeTrueTypeFonts
- 6 IncludeCIDFonts
For example, an embedded Type-1 font follows the rule for embedded fonts, not the rule for Type-1 fonts. In other words, if IncludeEmbeddedFonts is "true" , and IncludeType1Fonts is "false" , embedded Type-1 fonts would be included in the PostScript stream.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
|
If "true" , binary data are to be included in the PostScript stream. |
||
|
It is used for BoundingBox DSC comment in CenterCropBox calculations and for PostScript’s setpage Device. |
||
|
If "true" , the CropBox from the source document is centered on the page when the CropBox is smaller than MediaBox . |
||
|
If "true" , the Process emits individual streams of data for each page in the RunList . |
||
|
If "true" , ignores annotations that contain a PDF XObject form. (PDF source only). |
||
|
Ignores the BG , BG2 parameters in the PDF ExtGState dictionary, and the operand of any calls to the PostScript setblackgeneration operator. |
||
|
If "true" , ignores all Device-dependent extended graphic state parameters. This overrides IgnoreHalftones . The following parameters are to be ignored: |
||
|
If a PDF image Resource uses an external stream and IgnoreExternStreamRef = "true" , ignores code that points to the external file. (PDF source only). Note that IgnoreExternStreamRef was misspelled as IgnoreExternSreamRef prior to JDF 1.3. |
||
|
If "true" , ignores any halftone screening in the source file. |
||
|
Ignores OP parameters in a source PDF ExtGState dictionary setoverprint in a source PostScript file, etc. |
||
|
If "true" , ignores a “concatenation” provided at the beginning of each page that orients the page so that it is properly rotated. Used when emitting EPS. |
||
|
If "true" , no unnecessary filters are to be added when emitting image data. |
||
|
If "true" , and if emitting EPS, ignores only CMYK and gray images. |
||
|
If "true" , ignores save-and-restore showpage in PostScript files |
||
|
Ignores TR , TR2 parameters in a source PDF ExtGState dictionary, settransfer and setcolortransfer in a source PostScript file, etc. |
||
|
Ignores UCR , UCR2 parameters in a source PDF ExtGState dictionary, setundercolorremoval in a source PostScript file, etc. |
||
|
Determines when to embed the base fonts. The base fonts are Symbol and the plain, bold, italic and bold-italic faces of Courier , Times , and Helvetica . |
||
|
Determines when to embed fonts in the document that are embedded in the source file. This Attribute overrides the IncludeType1Fonts , IncludeTrueTypeFonts and IncludeCIDFonts Attributes. |
||
|
Determines when to include all other types of Resources in the file. |
||
|
Determines when to embed Type-3 fonts. It is included here to complete the precedence hierarchy. It has only one value. |
||
|
Number that indicates the PostScript level. Values include "1" , "2" or "3" . |
||
|
Number that indicates the wide-scale factor of documents. Full size = "100" . |
||
|
(PostScript Levels 2 and 3 only) If "true" , sets page size on each page automatically. For PDF source, use MediaBox for outputting PostScript files and CropBox for EPS. |
||
|
If "true" , indicates that if ProcSets are included, the init/term code is also included. |
||
|
If "true" , the page is scaled to fit the printer page size. This field overrides scale |
||
|
If "true" , suppresses automatic centering of page contents whose crop box is smaller than the page size. |
||
|
If "true" , suppresses automatic rotation of pages when their dimensions are better suited to landscape orientation. More specifically, the application that generates the PostScript compares the dimensions of the page. If the width is greater than the height, then pages are not rotated if SuppressRotate = "true" . On the other hand, if SuppressRotate = "false" , the orientation of each source page (e.g., as set by the PDF Rotate key) is honored, regardless of the dimensions of the pages (as defined by the MediaBox Attribute). |
||
|
If including TrueType fonts, converts to Type-42 instead of Type-1 fonts when TTasT42 = "true" . |
||
|
If "true" , font alias names are used when printing with system fonts. |
7.2.130 PDLCreationParams
This Resource is used to encapsulate the PDL output parameters for the supported output PDL types used in the PDLCreation Process.
|
This Resource identifies the MIME type associated with this output file format. For example "application/pdf" . |
||
|
Postscript specific Parameter Resource for the output. must not be specified unless MimeType = "application/postscript" |
||
|
PDF specific Parameter Resource for the output. It must not be specified unless MimeType = "application/pdf" |
7.2.131 PDLResourceAlias
This Resource provides a mechanism for referencing Resources that occur in files, or that are expected to be provided by Devices. Prepress and printing Processes have traditionally used the word “Resource” to refer to reusable data structures that are needed to perform Processes. Examples of such Resources include fonts, halftones and functions. The formats of these Resources are defined within PDLs, and instances of these Resources can occur within PDL files or can be provided by Devices.
JDF does not provide a syntax for defining such Resources directly within a Job. Instead, Resources continue to occur within PDL files and continue to be provided by Devices. However, since it is necessary to be able to refer to these Resources from JDF Jobs, the PDLResourceAlias Resource is provided to fulfill this need.
ColorantControl / ColorSpaceSubstitute
|
The type of PDL Resource that is referenced. The semantic of this Attribute is defined by the PDL. |
||
|
The name of the Resource in the file referenced by the FileSpec or by the Device. |
||
|
FileSpec ? |
Location of the file containing the PDL Resource. If FileSpec is absent, the Device is expected to provide the Resource defined by this PDLResourceAlias Resource. |
7.2.132 PerforatingParams
PerforatingParams define the parameters for perforating a Sheet.
7.2.132.1 Element: Perforate
Perforate describes one perforated line.
|
Relative starting position of the tool. The RelativeStartPosition is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0 for each component of the XYPair, which specifies the full size of the input Component . At least one of StartPosition or RelativeStartPosition must be specified. |
||
|
Relative working path of the tool beginning at RelativeStartPosition . Since the tools can only work parallel to the edges, one coordinate must be zero. The RelativeWorkingPath is always based on the complete size of the input Component and not on the size of an intermediate state of the folded Sheet. The allowed value range is from 0.0 to 1.0 for each component of the XYPair, which specifies the full size of the input Component . At least one of WorkingPath or RelativeWorkingPath must be specified. |
||
|
Starting position of the tool. If both StartPosition and RelativeStartPosition are specified, RelativeStartPosition is ignored. At least one of StartPosition or RelativeStartPosition must be specified. |
||
|
Number of teeth in a given perforation extent in teeth/point. MicroPerforation is defined by specifying a large number of teeth ( TeethPerDimension > 1000). |
||
|
Working path of the tool beginning at StartPosition . Since the tools can only work parallel to the edges, one coordinate must be zero. If both WorkingPath and RelativeWorkingPath are specified, RelativeWorkingPath is ignored. At least one of WorkingPath or RelativeWorkingPath must be specified. |
7.2.133 Person
This Resource provides detailed information about a person. It also has the ability to specify different communication channels to this person. Use @ ProductID when a unique identifier for the Person is required. The structure of the Resource is derived from the vCard format. It contains all of the same name subtypes (N:) of the identification and the title of the organizational properties. The corresponding XML types of the vCard are quoted in the description field of the table below.
Modification note: starting with JDF 1.4, a rule about using @ ProductID is added
|
Job function of the person in the company or organization (vCard: title). |
||
|
List of languages related to the person, ordered by decreasing preference |
||
|
Address ? |
||
7.2.134 PlaceHolderResource
This Resource is used to link Process Group Nodes when the exact nature of interchange Resources is still unknown. In this way, a skeleton of Process networks can be constructed, with the PlaceHolderResource Resources serving as place holders in lieu of the appropriate Resources. This Resource needs no structure besides that provided in an Abstract Resource Element as it has no inherent value except as a stand-in for other Resources.
7.2.135 PlasticCombBindingParams
This Resource describes the details of the PlasticCombBinding Process.
|
The name of the comb manufacturer and the name of the specific item. |
||
|
A more specific, specialized or site-defined name for the color. If ColorDetails is supplied, Color SHOULD also be supplied. |
||
|
The comb diameter is determined by the height of the block of Sheets to be bound. |
||
|
The distance between the “teeth” and the distance between the holes of the prepunched Sheets must be the same. The following values from the hole type catalog in Appendix L, “JDF/CIP4 Hole Pattern Catalog” exist: P12m-rect-02 - Distance = 12 mm; Holes = 7 mm x 3 mm Deprecated in JDF 1.2 P16-9i-rect-0t - Distance = 14.28 mm; Holes = 8 mm x 3 mm Deprecated in JDF 1.2 Euro - (Distance = 12 mm; Holes = 7 mm x 3 mm) Deprecated in JDF 1.1. USA1 - (Distance = 14.28 mm; Holes = 8 mm x 3 mm) Deprecated in JDF 1.1. Deprecation note: starting with JDF 1.2, use the value implied by HoleMakingParams /@ HoleType . |
||
|
Details of the holes to be made. Note that HoleMakingParams /@ Shape is always rectangular by design of the plastic combs. |
7.2.136 PlateCopyParams
See Section P.4.11, “PlateCopyParams” for details of this deprecated Resource.
7.2.137 PreflightAnalysis
This Resource was deprecated as a result of a major revision to the Preflight Process and its associated Resources. For details of this deprecated Resource see Section P.3.3, “PreflightAnalysis” .
7.2.138 PreflightInventory
This Resource was deprecated as a result of a major revision to the Preflight Process and its associated Resources. For details of this deprecated Resource see Section P.3.4, “PreflightInventory” .
7.2.139 PreflightParams
The PreflightParams Resource specifies the tests for the Preflight Process to run. These tests are defined using Section 7.3.2, “ActionPool” , which defines a list of reporting actions to have for given document object tests defined into a Test . (See Section 7.3.12, “TestPool” .) This section makes use of Elements and Attributes defined in Section 7.3, “Device Capability Definitions” . It is suggested that readers familiarize themselves with that section and Section 7.4, “Concept of the Preflight Process” .
|
A set of ActionPool Elements. Multiple ActionPool Elements are equivalent to one ActionPool that contains all Action Elements of the individual ActionPool Elements. |
||
|
Container for zero or more Test Elements that are referenced from Action Elements in the ActionPool . Although TestPool is New in JDF 1.3 , it is required because ActionPool implicitly requires a parallel TestPool as a container for the referenced Test Elements that are defined in Action /@ TestRef . |
The ActionPool , as defined in Section 7.3.2, “ActionPool” , has Action Subelements, which can reference a Test with a given action type. The Action Element includes a PreflightAction Subelement, defined below, which can be used to define how tests are to be applied in Preflight Processes.
7.2.139.1 Element: PreflightAction
|
A reference to a preflight Test ID used to filter a set of objects before applying the tests referenced by preflight Action . When SetRef is not defined, the Test is applied to all the objects. |
||
|
This is used to group objects in different ways. Page - Tests are applied on objects page per page. Document - Tests are applied on objects document per document. RunList - All objects of all pages included in all documents are processed together. Note: SetSplitBy is only used when SetRef is defined in order to create sets on a page-per-page or document-per-document basis. For instance, if you want to get the list of separations per page, SetSplitBy is set to "Page" . In such a case, the report’s content (as long as the PRItem is defined properly for the Action ) will be grouped by page. |
Test Elements make use of Evaluation Subelements that define various basic preflight testing functions that can be combined together in order to build preflight test. In order to specify basic preflight tests using Evaluation , the Subelement BasicPreflightTest is used. Note: The BasicPreflightTest includes a PreflightArgument Subelement that is defined below.
7.2.139.2 Element: BasicPreflightTest
The BasicPreflightTest Element defines a named preflight test that can be evaluated by a preflight application. The result of the test can be compared with the values defined in the explicit Evaluation Elements in order to filter the objects within the file to be tested. The following table describes the BasicPreflightTest Element.
|
List of object classes that the test MUST be applied to. It is strongly recommended to supply Classes |
||
|
This tag can be used to directly command the test to specifically apply on a given class of object. The two purposes of this change are 1) to simply preflight engine processors, and 2) to simplify Test rules. Values are from: Table 7-463, “Object Classes for a Document” . |
||
|
Namespace of the test that is described by Name in this BasicPreflightTest Element. |
||
|
Specifies what type of list or object the basic preflight test describes. Values are from: State /@ ListType ( Table 7.3.7, “State” ). Modification note: starting with JDF 1.4, ListType has a specified default value. |
||
|
Maximum number of elements in the list described by this BasicPreflightTest , (e.g., the maximum number of integers in an integer list). If MaxOccurs is not "1" , the BasicPreflightTest Element refers to a list or RangeList of values, (e.g., a NameEvaluation will allow a list of NMTOKENS). |
||
|
Minimum number of elements in the list described by this BasicPreflightTest . Default = "1" , (i.e., it is an individual value). If MinOccurs is not "1" , the BasicPreflightTest Element refers to a list or RangeList of values, (e.g., a NameEvaluation will allow a list of NMTOKENS). |
||
|
Local name of the preflight constraint that is evaluated by this BasicPreflightTest . A valid Name value for the JDF namespace is any property name defined in any of the Properties tables in Section 7.4.2, “Properties” Preflight tests are defined through the use of constraints. Modification note: starting with JDF 1.4, Name is no longer optional. |
||
|
Additional arguments for the preflight test. For details see Section 7.2.139, “PreflightParams” for the definition of PreflightArgument and constraints upon which preflight tests are defined. |
7.2.139.3 Element: PreflightArgument
This Subelement is used by BasicPreflightTest when additional data are needed to determine object property.
|
Used if BasicPreflightTest /@ Name has a value of either "InsideBox" and "OutsideBox" . Used for tests with the same two names. |
||
|
Used by the BoxToBoxDifference test. |
7.2.139.4 Element: BoxArgument
|
The box type used to verify inclusion or exclusion. Values are from: Table 7-296, “Box Attribute Values” . |
||
|
The MirrorMargins Attribute allows the flip of the Offset value depending on the RunList index. When the index is even, the original Offset value is preserved. When the index is odd, the Offset value is flipped. Default behavior: the value of Offset is not changed (if unspecified). |
||
|
Explains if overlap is allowed to check inclusion or exclusion. |
-- Attribute: Box
7.2.139.5 Element: BoxToBoxDifference
|
The “From” box used for BoxToBoxDifference calculation. Values are from: BoxArgument /@ Box |
||
|
The “To” box used for BoxToBoxDifference calculation. Values are from: BoxArgument /@ Box |
Example 7-43: Test with InsideBox and a BoxArgument Subelement
The following is an example of Test using InsideBox and a BoxArgument Subelement:
<JDF ID="ID" Type="ProcessGroup" xmlns="http://www.CIP4.org/JDFSchema_1_1"
Status="Waiting" JobPartID="ID34" Version="1.4">
<PreflightParams Class="Parameter" ID="PP001" Status="Available">
< BooleanEvaluation ValueList = "true" >
< BasicPreflightTest Name = "InsideBox" >
< BoxArgument Box = "TrimBox" Overlap = "true" />
<PreflightParamsLink Usage="Input" rRef="PP001"/>
7.2.140 PreflightProfile
This Resource was deprecated as a result of a major revision to the Preflight Process and its associated Resources. For details of this deprecated Resource see Section P.3.5, “PreflightProfile” .
7.2.141 PreflightReport
The PreflightReport Resource describes the results of the preflight tests specified in PreflightParams . This section makes use of Elements and Attributes defined in Section 7.3, “Device Capability Definitions” . It is suggested that reader’s familiarize themselves with that section and Section 7.4, “Concept of the Preflight Process” .
|
The count of errors that were encountered while preflighting the Job. |
||
|
Describes the type of errors that occurred during preflighting when the Preflight Process does not understand certain preflight tests or cannot apply them to the given objects. |
||
|
The count of warnings that were encountered while preflighting the Job. |
||
|
References the PreflightParams that was used to create this report. |
||
|
References the PreflightReportRulePool that was used to create this report. |
||
|
PRItem * |
Describes the Action Elements that produced an error or a warning. |
|
|
References the RunList that was used to create this report. |
7.2.141.1 Element: PRItem
The PRItem structure is used to describe the errors that occurred during the execution of one Action . When a Test could not be evaluated during the Preflight Process, this is reported as a PRError .
Objects that fail the preflight test are grouped together as described by a PRRule . During the Preflight Process, the number of objects and groups that are reported are limited to the maximum numbers defined in the PRRule .
When a PreflightReport is copied from one JDF document to another (e.g., a JDF writer might reduce the size of the PreflightReport by removing PRGroup and PROccurrence items within a PRGroup ), this will not invalidate the PreflightReport .
|
References the PreflightParams / ActionPool / Action that triggered this PRItem . |
||
|
The number of occurrences of objects that failed the Action . When the Action describes a set-test, this is the number of set-objects that failed the test. |
||
|
All run indices where there is an object that gives an error on that page. |
||
|
PRError * |
Describes the errors that were found while running this preflight test. |
|
|
PRGroup * |
Describes the Action Elements that produced an error or a warning. |
7.2.141.2 Element: PRError
The PRError structure is used to describe generic errors that occurred while evaluating an object property while executing a Test .
|
The name of the object property that was being tested when the Process error occurred. |
|
The PRGroup structure is used to describe a group of document objects that share common properties and that failed the Action .
|
The number of occurrences of objects of this group that failed the Action . When the Action Elements describes a set-test, this is the number of set-objects. |
||
|
All run indices where there is an object of this group that gives an error on that page. |
||
|
The properties that are shared by all Elements of the group as defined by PreflightReportRulePool / PRRule /@ GroupBy . |
||
|
An object that failed the Action . |
Depending on the test in the Action , the PRGroup is used in two different ways:
- When the test is not a set-test, there will be one level of PRGroup and PROccurrence Elements. These are used to describe all the document objects that failed the preflight test. The PROccurrence describes the actual object while PRGroup is used to group those objects that share common properties.
- When the test is a set-test, there will be two levels of PRGroup and PROccurrence Elements whereby the second level occurs as a child Element of PROccurrence .
- The top level describes the set objects that failed the preflight test. Just as in the non-set-test case, PROccurrence describes the actual set-objects while PRGroup is used to group those sets that share common properties. In the example below there are four page sets that failed the test, (e.g., pages 1, 4, 8 and 12).
- The second level, which is a child Element of the top level PROccurrence , describes the document objects that are part of the set. These document objects are grouped as well. In the example below page one consists of 20 objects: five text objects and 15 image objects.
Example 7-44: PRItem
<JDF ID="ID" Type="ProcessGroup" xmlns="http://www.CIP4.org/JDFSchema_1_1"
Status="Waiting" JobPartID="ID34" Version="1.4">
<PreflightReport Class="Parameter" ID="PP001" Status="Available"
ErrorCount="0" WarningCount ="0" >
< PRItem Occurrences = "4" ActionRef = "A001" >
< PRGroupOccurrence PageNumber = "1" />
< PROccurrence Occurrences = "20" >
< PROccurrence TextSize = "12" />
< PRGroup Occurrences = "15" >
< PROccurrence EffectiveResolution = "300 300" />
< PRGroupOccurrence PageNumber = "4" />
< PROccurrence Occurrences = "20" >
< PROccurrence NumberOfPathPoints = "4" />
< PRGroup Occurrences = "13" >
< PROccurrence EffectiveResolution = "300 300" />
< PRGroupOccurrence PageNumber = "8" />
< PRGroupOccurrence PageNumber = "12" />
<BooleanEvaluation ValueList="true"/>
<Action ID="A001" TestRef="T001"/>
<PreflightReportLink Usage="Input" rRef="PP001"/>
7.2.141.3 Element: Abstract PRGroupOccurrenceBase
Abstract PRGroupOccurrenceBase is an Abstract Element that serves as container for properties that were evaluated during the Preflight Process.
|
An example is given above. See also section Section 7.4.2, “Properties” and following. |
||
|
Example of an integer Attribute. The same format applies to boolean, Number, Name, NameList, enumeration, enumerations and string data types. |
7.2.141.4 Element: PRGroupOccurrenceBase
The following Elements are derived from the Abstract PRGroupOccurrenceBase Element
|
For additional arguments for a PRGroupOccurrence . |
||
|
Specifies shared Properties of all PROccurrence Elements in a PRGroup |
||
|
Describes an individual occurrence of a preflight action failure |
7.2.141.5 Element: ArgumentValue
ArgumentValue specifies a value that is specified with additional arguments. ArgumentValue is derived from Abstract PRGroupOccurrenceBase :
|
The argument that was used to evaluate this property. This is a PreflightArgument Element. (See Section 7.2.139.3, “PreflightArgument” .) |
7.2.141.6 Element: PRGroupOccurrence
PRGroupOccurrence specifies the shared properties of all PROccurrence Elements in a PRGroup . When the object does not support a certain property, the corresponding Attribute must not be specified in PRGroupOccurrence . PRGroupOccurrence is derived from Abstract PRGroupOccurrenceBase .
|
Describes the value of a property that is enhanced with additional arguments. |
7.2.141.7 Element: StringListValue
StringListValue specifies a type that returns a set of strings.
|
Value * |
Element of type StringEvaluation / Value . (See Section 7.3.13.6.2.13, “StringEvaluation” .) |
7.2.141.8 Element: PROccurrence
PROccurrence describes an individual occurrence of a preflight action failure. When the object does not support a certain property, the corresponding Attribute must not be specified in PROccurrence . PROccurrence is derived from Abstract PRGroupOccurrenceBase .
|
Only used when the subject occurrence is a set-object. It describes the number of objects in the set. |
||
|
PRGroup * |
When this occurrence describes a set-object, the PRGroup Elements describe the objects that are part of the set. |
7.2.142 PreflightReportRulePool
The PreflightReportRulePool Resource specifies how the PreflightReport is to log the errors that were found during the Preflight Process. This section makes use of Elements and Attributes defined in Section 7.3, “Device Capability Definitions” . It is suggested that reader’s familiarize themselves with that section and Section 7.4, “Concept of the Preflight Process” .
|
An upper bound to the maximum number of PROccurrence Elements that are to be logged in the PreflightReport . |
||
|
References the ActionPool whose reporting are defined by this rule. Deprecation note: starting with JDF 1.3 Errata, ActionPools is deprecated because PRRule / ActionRefs has the same role. |
||
|
PRRule * |
A list of available PRRule Elements. |
|
|
Defines the default behavior of all PRRule when not defined inside of a PRRule Subelement. |
7.2.142.1 Element: PRRule
The PRRule structure is used to define how the PreflightReport is to log the events that were found during the execution of one Action .
|
References the action for which the report behavior is defined in PRRule . |
||
The format of the PreflightReport is defined by specifying PRRule Elements for specific Action Elements. Because ActionRefs can refer to multiple Action Elements, a single rule applies to all referenced Action Elements, (e.g., all color-related Action Elements will use similar reporting).
7.2.142.2 Element: PRRuleAttr
|
Group objects having the same N-pair of Attributes listed here. |
||
|
ReportAttr = "Tested Filename PageNumber" |
When individual items are reported, these Attributes are also reported. Attributes which are also being referred by GroupBy are ignored. Values include those from: Table 7-311, “ReportAttr Attribute Values”. |
|
|
When the Preflight Process does not understand or cannot apply certain tests, that error must be logged when the associated type is logged here. The value is the sum of "TestWrongPDL" and "TestNotSupported" (these two returned values are explained in Section 7.4, “Concept of the Preflight Process” .) |
||
|
The maximum number of groups allowed in the report for this problem. When an object is encountered that fails the preflight test and it belongs to none of the existing groups and there are already MaxGroups , that occurrence is no longer reported individually and no new group is created, although it is added to the Occurrences count and the PageSet . |
||
|
The maximum number of individual occurrences reported per group for this problem. When an object is encountered that fails the preflight test and it belongs to a group that already contains MaxPerGroup Elements, that occurrence is no longer reported individually, although it is added to the Occurrences count and the PageSet . |
-- Attribute: ReportAttr
|
An object-specific Attribute, (e.g., ColorSpace , FontName , etc.). At the time that we define the Test , we will almost automatically define these Attributes. |
|
|
Refers to all the Attributes that are referred to in the Test Element(s) used by the Action Element(s) listed in the ActionRefs . |
|
|
Refers to all the Attributes referred in the Test Element(s) used by the Action Element(s) listed in ActionRefs and the ones that belong to the group of properties in which the tested property was found. For instance, if the Creator basic test was made, then all other document properties will be reported as well. |
|
|
Refers to a large list of Attributes that the preflight agent (with preflight agent-specific logic) finds interesting for the Test Element(s) used by the Action Element(s) listed in ActionRefs . |
|
|
Refers to a small list of Attributes that the preflight agent (with preflight agent-specific logic) finds interesting for the Test Element(s) used by the Action Element(s) listed in ActionRefs . |
When the report is generated, the "Tested" , "VerboseAppSpecific" and "BriefAppSpecific" terms are expanded depending on the context (i.e., the specific test and the specific preflight agent) so that the list of Attributes only contain object specific Attributes.
Note: The "VerboseAppSpecific" and "BriefAppSpecific" tokens can be dependent on the context of a specific test. It is expected that a preflight agent will have a default list of tokens that will always be added (e.g., "PageNumber" ). In addition it is expected that a preflight agent will define separate lists for specific domains, (e.g., color, font). When a specific test covers some of these specific domains, the Attributes of these lists are also added. When ReportAttr = "Tested BriefAppSpecific PageNumber" , the Attributes that are reported are dependent on the Test Element(s) used by the Action Element(s) and on the preflight agent as demonstrated in the table below.
When such an Attribute is evaluated against an object and when the Attribute is a property of the object, value will be recorded as an Attribute of the PROccurrence and PRGroupOccurrence Elements. When the Attribute is not a property of the object, no Attribute will be added to the PROccurrence and PRGroupOccurrence Elements. For example: TextSize on a text object would give < PROccurrence TextSize = "12" /> (assuming TextSize is defined as returning the size in points), but TextSize on an image would correspond to < PROccurrence /> .
7.2.143 Preview
The preview of the content of a surface. It can be used for the calculation of the ink coverage ( PreviewUsage = "Separation" ) or as a preview of what is currently processed in a Device ( PreviewUsage = "Viewable" or PreviewUsage = "ThumbNail" ). When the preview is of PreviewUsage = "Separation" or PreviewUsage = "SeparationRaw" , a gray value of "0" represents full ink, while a value of "255" represents no ink (for more information, see DeviceGray color model chapter 4.8.2 of the PostScript Language Reference Manual ) [PS] .
Any Element (generic content) , QueueEntry
PreviewType , Separation , SheetName , Side , TileID , WebName , RibbonName
InkZoneCalculation , PreviewGeneration
|
Compensation of the image to reflect the application of transfer curves to the image. Unknown - Deprecated in JDF 1.2 Film - Compensated until film exposure. |
||
|
Orientation of the Preview with respect to the Layout coordinate system . CTM is applied after any transformation defined within the referenced image file, (for example: the transformation defined in the CIP3PreviewImageMatrix of a PPF file). In case of PPF, CTM is applied to the native Postscript coordinate system of the preview. In case of PNG, the origin of the object is defined as the lower left corner of the image. |
||
|
Defines a base URL for the files that represent this Preview . If Directory is specified, it must be an Absolute URI [RFC3986] that implicitly also specifies a Base URI which is used to resolve any relative URL of Preview . See Appendix J, “Resolving RunList/@Directory and FileSpec/@URL URI References” and [FileURL] for examples. |
||
|
Specifies additional details of the preview's MIME type in case the value of PreviewFileType is a MIME type. |
||
|
PNG - The Portable Network Graphics format. CIP3Multiple - The format as defined in the CIP3 PPF specification. One or more previews per CIP3 file are supported. CIP3Single - The format as defined in the CIP3 PPF specification. Only one preview per CIP3 file is supported. Values are also: any MIME media type. See Appendix H, “MimeType and MimeTypeVersion Attributes”. New in JDF 1.4 Note: The CIP3 formats were added in JDF 1.2 only for backwards compatibility since many systems only support CIP3 format. The CIP3 formats must not be used except in Preview Resources that are used as Input Resources to InkZoneCalculation . Modification note: starting with JDF 1.4, the Data Type is changed from enumeration to string because MIME media types are added as values. |
||
|
Separation - Separated preview in medium resolution. SeparationRaw - Separated preview in medium resolution. SeparatedThumbNail - Very low resolution separated preview. ThumbNail - Very low resolution RGB preview. Viewable - RGB preview in medium resolution. Deprecation note: starting with JDF 1.2, PreviewType is still a Partition Key and must be used only as such -- as an Attribute of Preview , PreviewUsage (below) replaces PreviewType . |
||
|
PreviewUsage defines the semantics of the preview. Constraint: If both PreviewType as a Partition Key and PreviewUsage are specified, they must match. 3D - static 3D model New in JDF 1.4 Animation - animated previews for 3D display. New in JDF 1.4 Separation - Separated preview in medium resolution. Separation is generally used in InkZoneCalculation . SeparationRaw - Separated preview in medium resolution. This is identical to Separation except that no compensation has been applied. SeparationRaw is generally used for closed loop color control. SeparatedThumbNail - Very low resolution separated preview. |
||
|
URL identifying any preview file, (e.g., the PNG image or CIP3 PPF file that represents this Preview ). See [RFC3986] and Appendix J, “Resolving RunList/@Directory and FileSpec/@URL URI References” and Appendix M, “FileSpec Attributes and Container Subelement” for the syntax and examples. For the "file" URL scheme see also [RFC1738] and [FileURL] . Note: A preview will generally be Partitioned by separation, unless it represents an RGB viewable image or thumbnail. PPF files with multiple images can contain multiple Separations. In this case, the separation names defined in CIP3ADMSeparationNames define the separations and must match the Separation partion keys used in the JDF. |
7.2.144 PreviewGenerationParams
Parameters specifying the size and the type of the preview.
PreviewType , Separation , SheetName , Side , TileID , WebName , RibbonName
|
Policy that defines how to define the preview size if the aspect ratio of the source and preview are different. Note that AspectRatio only has an effect if Size is specified. CenterMax - Keep the aspect ratio and preview Size , and center the image so that the preview has missing pixels at both sides of the larger dimension. CenterMin - Keep the aspect ratio and preview Size , and center the image so that the preview has blank pixels at both sides of the smaller dimension. Crop - Keep the aspect ratio, and modify the preview size so that the image fits into a bounding rectangle defined by Size . Expand - Keep the aspect ratio, and modify the preview size so that the smaller image dimension is defined by Size . Ignore - Fill the preview completely, keeping Size , even if this requires modifying the aspect ratio. |
||
|
Compensation of the image to reflect the application of transfer curves to the image. Film - Compensated until film exposure. |
||
|
The file type of the preview to be generated. PNG - The Portable Network Graphics format. CIP3Multiple - The format as defined in the CIP3 PPF specification. One or more previews per CIP3 file are supported. CIP3Single - The format as defined in the CIP3 PPF specification. Only one preview per CIP3 file is supported. Note: The CIP3 formats were added in JDF 1.2 only for backwards compatibility since many systems only support CIP3 format. The CIP3 formats must not be used except in Preview Resources that are used as Input Resources to InkZoneCalculation . |
||
|
The kind of preview to be generated. Deprecation note: starting with JDF 1.1, PreviewType is still a Partition Key and must be used only as such -- as an Attribute of Preview , PreviewUsage (below) replaces PreviewType . |
||
|
The kind of preview to be generated. Separation - Separated preview in medium resolution. SeparationRaw - Separated preview in medium resolution with no compensation. SeparatedThumbNail - Very low resolution separated preview. ThumbNail - Very low resolution RGB preview. Viewable - RGB preview in medium resolution. Constraint: PreviewUsage defines the semantics of the preview. If both PreviewType as a Partition Key and PreviewUsage are specified, they must match. |
||
|
Resolution of the preview, in dpi. If PreviewUsage = "Separation" , the default is "50.8 50.8" . |
||
|
Size of the preview, in pixels. If this Attribute is present, the Resolution Attribute evaluated according to the policy defined in AspectRatio . If Size is not specified, it must be calculated using the Resolution Attribute and the input image size. |
||
|
Details of the ImageSetting Process. Needed for accessing information about coordinate transformations that are performed by the imagesetter hardware. |
7.2.145 PrintCondition
PrintCondition is a Resource used to control the use of colorants when printing pages on a specific media. The Attributes and Elements of the PrintCondition Resource describe the aim values for a given printing Process.
SignatureName , SheetName, Side, Separation
ConventionalPrinting , DigitalPrinting
|
Describes the desired tone-value increase function. If not specified, it defaults to the media and printing machine-specific values |
||
|
Density value of colorant (100% tint). Whereas Color / @NeutralDensity describes measurements of inks on substrate with wide-band filter functions, Density is derived from measurements of inks on substrate with special small band filter functions according to ANSI and DIN. If not specified, it defaults to the value of Color / PrintConditionColor /@ Density . |
||
|
Name of the PrintCondition . Used to reference a PrintCondition from a Color / PrintConditionColor Element. |
||
|
Describes measurement conditions for color measurement and density measurement. If not specified, it defaults to the value of Color / PrintConditionColor / ColorMeasurementConditions |
||
|
Device ? |
Specifies the Device or Device group that this PrintCondition applies to. |
|
|
FileSpec ( TargetProfile ) ? |
A FileSpec Resource pointing to an ICC profile that defines the target output Device in case the object that uses the Color has been color space converted to a Device color space. If not specified, it defaults to the value of Color / PrintConditionColor / FileSpec ( TargetProfile ). |
Example 7-45: PrintCondition
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< ColorMeasurementConditions Class = "Parameter" ID = "MyColorMeasCond"
< PrintCondition Name = "Standard" Class = "Parameter" ID = "PC"
PartIDKeys = "Side Separation" Status = "Available" >
< ColorMeasurementConditionsRef rRef = "MyColorMeasCond" />
< PrintCondition Side = "Front" >
< PrintCondition AimCurve = "0.0 0.0 0.5 0.66 1.0 1.0" Density = "1.8"
< PrintCondition AimCurve = "0.0 0.0 0.5 0.63 1.0 1.0" Density = "1.4"
<PrintConditionLink Usage="Input" rRef="PC"/>
7.2.146 PrintRollingParams
|
7.2.147 ProductionPath
ProductionPath describes the individual paper path through the different modules of a Web-Press Device, in order to produce a particular product.
CylinderLayoutPreparationParams
|
Unique identification of the entire production path. If not specified, PrintingUnitWebPath must be specified. |
||
|
Describes the path through the folder super-structure. The Web will generally be cut into ribbons in this area of the production path. |
||
|
Describes the path through the inline postpress equipment. Folded Sheets ( Component ) will be processed in this area of the production path. |
||
|
Describes the path through the printing units. If not specified, ProductionPathID must be specified. |
7.2.147.1 Element: FolderSuperstructureWebPath
This is a placeholder that might be filled with additional information in future versions of JDF. In JDF 1.3, paths are identified by ID only.
|
Unique identification of the part of the production path specified in this Element. |
7.2.147.2 Element: PostPressComponentPath
This is a placeholder that might be filled with additional information in future versions of JDF. In JDF 1.3, paths are identified by ID only.
|
Unique identification of the part of the production path specified in this Element. |
7.2.147.3 Element: PrintingUnitWebPath
This is a placeholder that might be filled with additional information in future versions of JDF. In JDF 1.3, paths are identified by ID only.
|
Unique identification of the part of the production path specified in this Element. |
Example 7-46: ProductionPath: on Path Level:
This example and the next illustrate the different Web path description levels:
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< ProductionPath Class = "Parameter" ID = "F1" Status = "Available"
ProductionPathID = "ID_2webproduction_64pages" />
Example 7-47: ProductionPath: on Part Path Level:
This example and the previous illustrate the different Web path description levels:
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< ProductionPath Class = "Parameter" ID = "F1" Status = "Available"
< ProductionPath WebName = "1" >
< PrintingUnitWebPath ProductionPathID = "ID_PrintingUnitWebPath" />
< FolderSuperstructureWebPath ProductionPathID = "abcd" />
< PostPressComponentPath ProductionPathID = "xyz" />
<ProductionPathLink Usage="Input" rRef="F1"/>
7.2.148 ProofingParams
In JDF 1.2 and beyond, proofing is handled as a Combined Process. For detail of this deprecated Resource, see Section P.4.12, “ProofingParams” .
7.2.149 PSToPDFConversionParams
This Resource contains the parameters that control the conversion any PDL to PDF documents. Prior to JDF 1.3, PSToPDFConversionParams was used only for converting PostScript streams to PDF. The name “ PSToPDFConversionParams ” was retained for backwards compatibility, although most parameters apply to PDF conversion from any source format.
Some descriptions below mention Attributes or structures in specific source formats, such as PostScript. Appropriate equivalent actions should be taken when converting from other source formats that have equivalent Attributes or structures. A small number of parameters apply only to PostScript sources.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
|
This Resource allows JBIG2 compressed images to share a single global dictionary in the resulting PDF file instead of a dictionary per image. |
||
|
If "true" , binary streams (e.g., page contents streams, sampled images, and embedded fonts) are ASCII85-encoded, resulting in a PDF file that is almost pure ASCII. If "false" , they are not, resulting in a PDF file that can contain substantial amounts of binary data. |
||
|
Allows the Device to try to orient pages based on the predominant text orientation. If the source is PostScript, this Attribute is only used if the file does not contain “%%ViewingOrientation”, “%%PageOrientation” or “%%Orientation” DSC comments. If the file does contain such DSC comments, it honors them. “%%ViewingOrientation” takes precedence over others, then “%%PageOrientation”, then “%%Orientation”. None - Turns AutoRotatePages off. All - Takes the predominant text orientation across all pages and rotates all pages the same way. PageByPage - Does the rotation on a page-by-page basis, rotating each page individually. Useful for documents that use both portrait and landscape orientations. |
||
|
Enables compression of pages and other content streams like forms, patterns and Type 3 fonts. If "true" , use Flate compression. |
||
|
Selects the rendering intent for the current Job. Note: See the Portable Document Format Reference Manual for more information on rendering intent. |
||
|
Enables or disables blend detection. If "true" and if PDFVersion is 1.3 or higher, then blends will be converted to smooth shadings. |
||
|
Number that indicates the last page that is displayed when the PDF file is viewed. EndPage must be either "-1" or greater than or equal to StartPage . When combined with StartPage , EndPage selects a range of pages to be displayed. The entire file may be converted, but only StartPage to EndPage pages, inclusive, are opened and viewed in a PDF viewing application. |
||
|
Number of bytes in the buffer used in sample processing for color, grayscale and monochrome images. Its contents are written to disk when the buffer fills up. This Attribute was deprecated because it is an internal application setting and not a parameter setting. |
||
|
Defines the initial page dimensions, in points, that will be used to set MediaBox. This will be overridden by any page size Attribute found in the source document, such as the PostScript PageSize page Device parameter. The use of this Attribute is strongly encouraged when processing EPS files (%%BoundingBox comments do not override InitialPageSize ). |
||
|
Defines the initial horizontal and vertical resolution, in dpi. This will be overridden by any resolution Attribute found in the source document, such as the PostScript HWResolution page Device parameter. The use of this Attribute is strongly encouraged when processing EPS files. |
||
|
Controls the overprint mode strategy of the Job. Set to "0" for full overprint or "1" for non-zero overprint. For more information, see [Adb-TN5044] . |
||
|
If "true" , the PS-to-PDF converter optimizes the PDF file. See [PDF1.6] for more information on optimization. |
||
|
Specifies the version number of the PDF file produced. Values include all legal version designators, (e.g., 1.2, 1.5). |
||
|
Sets the first page that is be displayed when the PDF file is opened with a PDF viewing application. StartPage must be greater than or equal to 1. EndPage must be either "-1" or greater than or equal to StartPage . |
||
|
Advanced parameters which control how certain features of PDF are handled. |
||
|
Parameters that control the optional content or form of PDF files that will be created. |
7.2.149.1 Element: AdvancedParams
|
If "true" , the Process automatically resizes and centers information from EPS source files on the page. (EPS source only) |
||
|
If "true" , the PDF settings used to create the PDF are embedded in the PDF. |
||
|
If "true" , warning messages about questionable or incorrect DSC comments appear during the processing of the source PostScript file. (PostScript source only) |
||
|
If "true" , any PSToPDFConversionParams settings configured by the source content (e.g., with setdistillerparams in a PostScript source document) are ignored. If "false" , each parameter defined in the source document overrides that set in the JDF. 
|
||
|
If "true" , the Process parses the DSC comments in a PostScript source document for any information that might be helpful for converting the file or for information that is to be stored in the PDF file. If "false" , the Process treats the DSC comments as pure PS comments and ignores them. (PostScript source only) |
||
|
If "true" , the Process parses the DSC comments in a PostScript source file and extracts the document information. This information is recorded in the Info dictionary of the PDF file. |
||
|
If "true" , JPEG images are passed through without recompressing them. |
||
|
If "true" , the copypage operator of PostScript Level 2 is maintained. If "false" , the PostScript Level 3 definition of copypage operator is used. In PostScript Levels 1 and 2, the copypage operator transmits the page contents to the current output Device (similar to showpage ). However, copypage does not perform many of the re-initializations that showpage does. Many PostScript Level 1 and 2 programs used the copypage operator to perform such operations as printing multiple copies and implementing forms. These programs produce incorrect results when interpreted using the Level 3 copypage semantics. This Attribute provides a mechanism to retain Level 2 compatibility for this operator. (PostScript source only) |
||
|
If "true" , preserves the EPS information in a PostScript source file and stores it in the resulting PDF file. (PostScript source only) |
||
|
If "true" , passes halftone screen information (frequency, angle and spot function) into the PDF file. If "false" , halftone information is not passed in. |
||
|
If "true" , passes the value of the setoverprint operator through to the PDF file. Otherwise, overprint is ignored. |
||
|
If "true" , encapsulates Open Prepress Interface (OPI) low resolution images as a form and preserves information for locating the high resolution images. |
||
|
Determines how transfer functions are handled. Preserve - Transfer functions are passed into the PDF file. Remove - Transfer functions are ignored. They are neither applied to the color values nor passed into the PDF file. Apply - Transfer functions are used to modify the data that are written to the PDF file, instead of writing the transfer function itself to the file. |
||
|
Determines whether the under-color removal and black-generation parameters from the source document (e.g., the arguments to the PostScript commands setundercolorremoval and setblackgeneration ) are passed into the PDF file. |
||
|
If "true" , the Process must append a PostScript prologue file before beginning of the Job and append a PostScript epilog file after the end the Job. Such files are used to control the PostScript environment for the conversion Process. The expected location and allowable contents for these files is defined by the Process implementation. (PostScript source only) |
7.2.149.2 Element: PDFXParams
Parameters for generating PDF/X files. Note that TrimBox, BleedBox, output intent and the Trapped state may be provided by the use of the pdfmark operator in a PostScript source file.
|
If "true" , checks compliance with the PDF/X- 1a standard [ISO15930-1:2001] . |
||
|
If "true" , checks compliance with the PDF/X-3 standard [ISO15930-3:2002] . |
||
|
If the BleedBox entry is not specified in the page object of the source document, BleedBox is set to PDF TrimBox with offsets. All numbers must be greater than or equal to 0.0. PDF BleedBox will be completely outside PDF TrimBox . |
||
|
If "true" , produces a PDF document only if PDF/X compliance tests are passed. |
||
|
The string is an optional comment which is added to the PDF file. It describes the intended printing condition in a form that ought to be meaningful to a human operator at the site receiving the PDF document. |
||
|
If the source document does not specify an output intent name, then this value is used. Values include those from: Table 7-324, “PDFXOutputIntentProfile Attribute Values”. |
||
|
If "true" and both TrimBox and ArtBox entries are not specified in the page object of the source document, the condition is reported as an error. |
||
|
Indicates a location at which more information regarding the registry that defines the OutputConditionIdentifier can be obtained. |
||
|
If "true" and the BleedBox entry is not specified in the page object of the source document, BleedBox is set to MediaBox . |
||
|
If a source document does not specify a Trapped state, then the value provided here is used. The value Unknown is to be used for workflows requiring 1) that the document specify a Trapped state and 2) that compliance checking fail if Trapped is not present in the document. |
||
|
If both the TrimBox and ArtBox entries are not specified in the page object of the source document, TrimBox is set to MediaBox with offsets. All numbers must be greater than or equal to 0.0. The TrimBox will be completely inside MediaBox . |
-- Attribute: PDFXOutputIntentProfile
|
Used when it is required that the source document specifies an intent; allows compliance checking to fail |
|
7.2.149.3 Element: ThinPDFParams
7.2.150 QualityControlParams
This set of parameters identifies how the QualityControl Process is to operate. The QualityControlParams defines the generic set of parameters for the quality control Process. The specific measurement conditions are defined in specialized Subelements such as BindingQualityParams .
|
Specification of the definition parameters of one individual Resource. |
7.2.151 QualityControlResult
This set of parameters returns results of a QualityControl Process. The QualityControlResult defines the generic set of results from the quality control Process. The specific measurements are returned in specialized Subelements such as BindingQualityParams . Additional detailed quality control result types are anticipated in future versions of the JDF specification.
|
FileSpec ? |
Location of an external file that contains details of the quality control measurement. |
|
7.2.151.1 Element: QualityMeasurement
QualityMeasurement Elements describe an individual measurement.
|
Date and time of the end of the measurement. If not specified, the value of Start is applied. |
||
|
Condition of the tested Component . If the Component passed the test, but the test itself destroyed the Component , the value is to be set to "destroyed" . |
||
|
Date and time of the start of the measurement. If not specified, the measurement time is not known. |
||
|
Details of the BindingQualityMeasurement . |
7.2.152 RasterReadingParams
This set of parameters specifies the details for RasterReading .
|
Indicates whether or not the finished page image is to be centered within the imageable area of the media. The Center is ignored if FitPolicy /@ SizePolicy = "ClipToMaxPage" and clipping is requested. |
||
|
This Attribute specifies the axis around which a raster reader is to mirror an image. FeedDirection - Image is mirrored around the feed-direction axis. |
||
|
The image must be RIPed in the polarity specified. Note that this is a polarity change in the RIP and not a polarity change in the hardware of the output Device. |
||
|
Specifies whether the page contents is to be expanded such that each page covers X by Y pieces of media. |
||
|
This pair of real numbers identifies the amounts of overlap in points, that specify the poster tiles across the horizontal and vertical axes, respectively. |
||
|
A pair of positive real values that indicates the scaling factor for the page contents. Values between 0 and 1 specify that the contents are to be reduced, while values greater than 1 specify that the contents are to be expanded. This Attribute is ignored if FitToPage = "true" or if Poster is present and has a value other than "1 1" . Any scaling defined in FitPolicy must be applied after the scaling defined by this Attribute. |
||
|
A pair of real values that identify the point in the unscaled page that is to become the origin of the new, scaled page image. This point is defined in the coordinate system of the unscaled page. If not specified, and scaling is requested, the ScalingOrigin defaults to "0 0" |
||
|
Allows printing even if the size of the imageable area of the media does not match the requirements of the data. This replaces the deprecated FitToPage Attribute. This FitPolicy Resource must be ignored in a Combined Process with LayoutPreparation . |
||
|
Media * |
This Resource provides a description of the physical media which will be marked. The physical characteristics of the media may affect decisions made during RasterReading . The cardinality was changed to “*” in JDF 1.2 in order support description of multiple media types, (e.g., Film, Plate and Paper.) If multiple Media are specified, The Media /@ MediaType defines the type of Media . If multiple Media with Media /@ MediaType = "Paper" are specified in a proofing environment, the first Media is the proofer paper and the second Media is the final Device paper. |
7.2.153 RefAnchor
RefAnchor describes the relative position with respect to a related element in a layout. Depending on the value of AnchorType , it specifies either a parent Element or a sibling Element.
Layout / MarkObject , LayoutElementProductionParams / LayoutElementPart / PositionObj , StrippingParams / StripMark
|
Anchor specifies the origin (0,0) of the vector specified in the rotated coordinate system of the related layout element. |
||
|
Role of this RefAnchor . Parent - The layout element referenced by this RefAnchor is a parent. This layout element is transformed with the parent. Sibling - The layout element referenced by this RefAnchor is a sibling. Both layout elements share a common parent. The parent of this layout element is specified as the RefAnchor of the first child in the chain of siblings. |
||
|
Reference to a layout element that this layout element is positioned by. if rRef is not specified, the page or sheet defined by the layout element is the parent container. |
7.2.154 RegisterMark
Defines a register mark, which can be used for setting up and monitoring color registration in a printing Process. It can also be used to synchronize the Sheet position in a paper path. The position and rotation of each register mark can be specified with the help of the following Attributes. It is important that the register marks are defined in such a way that their centers are on the point of origin of the coordinate system, as otherwise they are not positioned properly.
HoleMakingParams , Layout / MarkObject
|
Position of the center of the register mark in the coordinates of the MarkObject that contains this mark. |
||
|
Type of RegisterMark . Modification note: starting with JDF 1.4, the data type changes from NMTOKEN to NMTOKENS. |
||
|
Specifies the usage of the RegisterMark . Color - The mark is used for separation color registration. PaperPath - The mark is used for paper path synchronization. Tile - The mark is used to mark the position of tiles in Tiling. New in JDF 1.4 |
||
|
Rotation in degrees. Positive graduation figures indicate counter-clockwise rotation; negative figures indicate clockwise rotation. |
||
7.2.155 RegisterRibbon
Description of register ribbons. For the register ribbon, the length must be specified. There are two parameters, as shown in Figure 7-52, “RegisterRibbon lengths and coordinate system for BlockPreparation”:
BindingIntent / HardCoverBinding , BindingIntent / BindList / BindItem / HardCoverBinding , BlockPreparationParams
|
Overall length of the register ribbon, (i.e., VisibleLength + HiddenLength in Figure 7-52). Note “HiddenLength” is not an Attribute Modification note: starting with JDF 1.4, LengthOverall is optional. |
||
|
A more specific, specialized or site-defined name for the color. If RibbonColorDetails is supplied, RibbonColor SHOULD also be supplied. |
||
|
SealedOffset - The ribbon is sealed a distance from the cut. |
||
|
Length of the register ribbon which will be seen when opening the book, (See Figure 7-52). Modification note: starting with JDF 1.4, VisibleLength is optional. |
|
7.2.156 RenderingParams
This set of parameters identifies how the Rendering Process is to operate. Specifically, these parameters define the expected output of the ByteMap Resource that the Rendering Process creates.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
|
Height of output bands expressed in lines. For a frame Device, the band height is simply the full height of the frame. |
||
|
Indicates whether output buffers are generated in BandMajor or ColorMajor order. BandMajor - The position of the bands on the page is prioritized over the color. ColorMajor - All bands of a single color are played in order before progressing to the next plane. This is only possible with non-interleaved data. |
||
|
Number of bits per colorant. Determines whether the output is bitmaps or bytemaps. |
||
|
If "true" , the resulting colorant values are interleaved and BandOrdering is ignored. |
||
|
Controls for overprint substitutions. Defaults to no automated overprint generation. |
||
|
Elements which define the resolutions to render the contents at. More than one Element may be used to specify different resolutions for different SourceObjects types. If no ObjectResolution is specified, the value is implied from the input data. |
||
|
Media ? |
This Resource provides a description of the physical media which will be marked. The physical characteristics of the media may affect decisions made during Rendering . In JDF 1.2 and beyond, a RIP is to obtain Media information from InterpretingParams / Media . |
7.2.157 ResourceDefinitionParams
This set of parameters identifies how the ResourceDefinition Process is to operate. Specifically, these parameters define how default parameters of applications and the Input Resource are to be combined.
7.2.157.1 Element: ResourceParam
|
Resource /@ ID of the default Resource. If missing, it is assumed that the file specified by DefaultJDF contains only a JDF Resource Element, not a complete JDF. |
||
|
Link to a JDF Resource that defines preset values. Defaults to the DefaultJDF specified in ResourceDefinitionParams . |
||
|
Defines whether preset values of the application or of the Resource specified in DefaultJDF have priority. Default value is from: parent’s ResourceDefinitionParams /@ DefaultPriority. |
7.2.158 RingBindingParams
This Resource describes the details of the RingBinding Process.
|
A more specific, specialized or site-defined name for the color. If BinderColorDetails is supplied, BinderColor SHOULD also be supplied. |
||
|
The following describe RingBinding binder materials used. Cardboard - Cardboard with no covering. |
||
|
The name of the binder manufacturer and the name of the specific item. |
||
|
RingBinding values: |
||
|
Deprecation note: starting with JDF 1.2, use the value implied by HoleMakingParams /@ HoleType . |
||
|
The following RingBinding choice describes mounting of ring mechanism in binder case. If "true" , the heads of the rivets are visible on the exterior of the binder. If "false" , the binder covering material covers the rivet heads. |
||
|
A more specific, specialized or site-defined name for the color. If SpineColorDetails is supplied, SpineColor SHOULD also be supplied. |
||
|
The spine width is determined by the final height of the block of Sheets to be bound. |
||
|
For RingBinding clear vinyl outer-wrap types on top of a colored base wrap: Embedded - Printed material is embedded by sealing between the colored and clear vinyl layers during the binder manufacturing. Pocket - Binder is designed so that printed material can be inserted between the color and clear vinyl layers after the binder is manufactured. |
||
|
Details of the holes in RingBinding . |
7.2.160 RunList
RunList Resources describe an ordered set of LayoutElement or ByteMap Elements. Ordering and structure are defined using the generic Partitioning mechanisms as described in Section 3.10.5, “Description of Partitioned Resources”.
RunList Resources are used whenever an ordered set of page descriptions Elements are specified. Depending on the Process usage of a RunList , only certain types of LayoutElement may be valid. For example, a pre-RIP Imposition Process requires LayoutElement Elements whose ElementType is either "Page" or "Document" , whereas a post-RIP Imposition Process requires ByteMap Elements. The usage is detailed in the descriptions of the Processes that use the RunList Resource. RunList Resources allow structuring of multiple Pages into Documents . Multiple Documents that have a joint context may be grouped into Sets .
In essence, a RunList is a virtual document or set of documents. It allows a document to either be physically spread over multiple files, or multiple documents to be contained within a single file (e.g. PPML, PDF/VT). It retains the same properties as the original documents, e.g. the pages of a document that is described by a RunList are ordered.
ArtDeliveryIntent / ArtDelivery , DigitalMedia , Layout / PageCondition , Layout / SheetCondition , PreflightReport
PartVersion , Run , RunPage , RunSet , Separation , WebProduct
AssetListCreation , ColorCorrection , ColorSpaceConversion , ContoneCalibration , CylinderLayoutPreparation , DigitalDelivery , DigitalPrinting , FormatConversion , ImageReplacement , ImageSetting , Imposition , Interpreting , LayoutPreparation , LayoutShifting , PageAssigning , PDFToPSConversion , PDLCreation , Preflight , PreviewGeneration , PSToPDFConversion , RasterReading , Rendering , Screening , Separation , Stripping , Tiling , Trapping
AssetListCreation , ColorCorrection , ColorSpaceConversion , ContoneCalibration , DBTemplateMerging , DigitalDelivery , FormatConversion , ImageReplacement , Imposition , Interpreting , LayoutElementProduction , LayoutPreparation , LayoutShifting , PageAssigning , PDFToPSConversion , PDLCreation , PSToPDFConversion , RasterReading , Rendering , Scanning , Screening , Separation , Stripping , Tiling , Trapping
|
Specifies which grouping of input LayoutElement PDL pages define the equivalent of an individual output Component instance for processing in a multi-document print Job, e.g., in a variable data Job. For instance, all pages defined between end-of-set markers would be stitched in a Combined Process Node with DigitalPrinting and Stitching Processes if ComponentGranularity = "Set" . All - The complete RunList , regardless of document or set breaks defines a new Component . BundleItem - An implicit PDL-defined document break or an explicit EndOfBundleItem defines a new Component . Document - An implicit PDL-defined document break or an explicit EndOfDocument defines a new Component . Page - Each page in the RunList defines a new Component . Set - Each set as defined by an implicit PDL-defined set break or an explicit EndOfSet defines a new Component . |
||
|
Defines a directory where the files that are associated with this RunList are to be copied to or from. If Directory is specified, it must be an Absolute URI [RFC3986] that implicitly also specifies a Base URI which is used to resolve any relative URL of RunList . See Appendix J, “Resolving RunList/@Directory and FileSpec/@URL URI References” and [FileURL] for examples. |
||
|
Number of Instance Document copies that this RunList represents. Specifying DocCopies is equivalent to repeating the sequence of RunList leaves between EndOfDocument = "true" for a total of DocCopies times. If DocCopies is > 1 for an automated imposition job, the imposition engine places the equivalent DocCopies Attribute into the RunList ( Surfaces ) Resource generated by the Imposition Process. An exception is cut-and-stack imposition, where DocCopies is applied by the imposition engine itself, and not placed into the RunList ( Surfaces ). Note: It is illegal to specify DocCopies with different values of various leaves of a RunList representing the same Instance Document. |
||
|
A list of named documents in a multi-document file that supports named access to individual documents. The DocNames defaults to all documents. If DocNames occurs in the RunList , Docs is ignored if it is also present. |
||
|
Zero-based list of document indices in a multi-document file specified by the LayoutElement Resource. |
||
|
If "true" , the last page in the RunList is the last page of a BundleItem . The implied default value of EndOfBundleItem = "false", except for the last RunList Partition, which always has an implied default value of EndOfBundleItem = "true" . Modification note: starting with JDF 1.4, this Attribute no longer depends on the deprecated ComponentGranularity . |
||
|
If "true" , the last finished page in the RunList is the last page of an Instance Document. The precise handling of Instance Document changes is defined in the InsertSheet Resource. If the RunList references a PDL that supports internal Instance Documents, EndOfDocument may be implied from the PDL. The implied default value of EndOfDocument = "false", except for the last RunList Partition leaf, which always has an implied default value of EndOfDocument = "true" . |
||
|
If "true" , the last finished page in the RunList is the last page of a set of Instance Documents. The precise handling of Instance Document boundaries is defined in the InsertSheet Resource. If the RunList references a PDL that supports internal sets, EndOfSet may be implied from the PDL. The implied default value of EndOfSet = "false", except for the last RunList Partition leaf, which always has an implied default value of EndOfSet = "true" . |
||
|
First finished page in the document that is described by this RunList . This Attribute is generally used to describe preseparated files. |
||
|
Specifies the PartIDKeys values that do not affect the context in which this RunList is processed. Typically used when the ResourceLink is Partitioned to re-order a content RunList . For the keys specified in this list, processing the RunList MUST operate as if the identified parts represent the entire RunList . If Partition Keys are not specified, processing the RunList MUST operate as if the entire RunList Resource was processed, and all results removed except for those identified by the ResourceLink (e.g. for reprinting or recreating sheets with processing order-sensitive content - SheetIndex has whatever value it would have had if sheets were generated using the entire, original RunList ). See example just below this table. |
||
|
If "true" , the individual RunList Resource defines one or more page slots, (e.g., for filling PlacedObject Elements). If "false" , the first parent Partitioned RunList Resource with IsPage = "true" defines the page level. In general, IsPage = "false" for separations of a preseparated RunList . |
||
|
The logical page number of the first finished page in a RunList . This Attribute may be used to retain logical page indices when a Partitioned RunList is spawned. It defaults to "1" plus the last finished page of the previous sibling RunList Partition. If the RunList Resource is the first Partition, LogicalPage defaults to "0" . Note that is an error to specify LogicalPage to be less than the number of previously defined logical pages in the same Partition, since this defines overlapping finished pages within the RunList Partition. |
||
|
Total number of Instance Documents that are defined by the RunList . If NDoc is not specified, it defaults to all Instance Documents in the Partitioned RunList Elements that make up the RunList . |
||
|
Total number of pages (placed object slots or RunList Elements with IsPage = "true" ) that are defined by the RunList . If NPage is not specified, it defaults to all finished pages in the Partitioned RunList Elements that make up the RunList . If the RunList describes multiple Instance Documents or Document Sets, NPage refers to the total number of finished pages in all Instance Documents and sets. A RunList with NPage specified always refers to NPage pages, regardless of the number of pages of the referenced PDL. If NPage is not specified and no content is referenced, the RunList contains exactly one page. |
||
|
Total number of Instance Document Sets that are defined by the RunList . If NSet is not specified, it defaults to all Instance Document Sets in the Partitioned RunList Elements that make up the RunList . |
||
|
Number of finished page copies that this RunList represents. Specifying PageCopies is equivalent to repeating the RunList leaves representing each page for a total of PageCopies times (e.g., a multiple represented by the value of PageCopies .) Note that pages specified by PageCopies are always assumed uncollated when calculating the index in the logical RunList , (e.g., PageCopies = "2" would result in a logical page sequence of 0 0 1 1 2 2, etc.). |
||
|
List of the indices of the PageData Elements of the PageList specified in the LayoutElement referenced by this RunList . If not specified, the complete PageListIndex specified in the LayoutElement referenced by this RunList is applied. |
||
|
A list of named pages in a multi-page file that supports named access to individual finished pages. The PageNames defaults to all pages. If PageNames is specified, then FirstPage , NPage , SkipPage and Pages must all be ignored if any is specified. |
||
|
Zero-based list of indices in the documents specified by the LayoutElement Resource and the Docs , DocNames , Sets and SetNames Attributes. The Pages need not be in document order. If Pages is specified, FirstPage and SkipPage must be ignored. If none of Pages , FirstPage , NPage , PageNames or SkipPage is specified, all pages (i.e., "0 ~ -1" ) referred to by the RunList are selected. Modification note: before JDF 1.4, LayoutElement appeared in place of RunList in the preceding sentence. |
||
|
Tag of a Partition of a Resource other than the RunList which is Partitioned by RunTags . The Partition matches if any of the entries in the RunTags list matches RunTag. Multiple entries in a RunList may have the same RunTag . If the RunList references a PDL that supports internal labels, RunTag may be implied from the PDL. |
||
|
Number of Instance Document Set copies that this RunList represents. Specifying SetCopies is equivalent to repeating the sequence of RunList leaves between EndOfSet = "true" for a total of SetCopies times. If SetCopies is > 1 for an automated imposition Job, the imposition engine places the equivalent SetCopies Attribute into the RunList ( Surfaces ) Resource generated by the Imposition Process. An exception is cut-and-stack imposition, where SetCopies is applied by the imposition engine itself, and not placed into the RunList ( Surfaces ). Note: it is illegal to specify SetCopies with different values of various leaves of a RunList representing the same Instance Document. |
||
|
A list of named Document Sets in a multi-Document Set file that supports named access to individual documents. The SetNames defaults to all Document Sets specified by Sets . If SetNames occurs in the RunList , Sets is ignored if it is also present. SetNames is only valid if LayoutElement /@ ElementType = "MultiSet" . |
||
|
Zero-based list of Document Set indices in a multi-Document Sets file specified by the LayoutElement Resource. If not present, all Document Sets are selected. Sets is only valid if LayoutElement /@ ElementType = "MultiSet" . |
||
|
Specifies the binding of surfaces referenced by this RunList to sheets. MUST only be specified in RunList ( Surfaces ). Front - all surfaces referenced from a RunList leaf Partition describe one or more front sides of successive sheets, with implicit back blank sides. Back - all surfaces referenced from a RunList leaf Partition describe one or more back sides of successive sheets, with implicit front blank sides. FrontBack - all surfaces referenced from a RunList leaf Partition describe a succession of sheets, where for each sheet a front is followed by a back surface. BackFront - all surfaces referenced from a RunList leaf Partition describe a succession of sheets , where for each sheet a back is followed by a front surface. |
||
|
Used when the RunList comprises every Nth page of the file. SkipPage indicates the number of finished pages to be skipped between each of the pages that comprise the RunList Resource. This is generally used to describe preseparated files, or to select only even or odd pages. Note that SkipPage is, therefore, 3 (4 Separations -> skip 3) in a CMYK separated file. |
||
|
Specifies whether the Elements in the RunList are sorted in the document reader order. |
||
|
ByteMap ? |
Describes the page or stream of pages. At most one of ByteMap , InterpretedPDLData or LayoutElement must be specified. If none of ByteMap , InterpretedPDLData or LayoutElement are specified, the RunList specifies empty content. |
|
|
Indicates what the Device should do with the file when the Process that uses this Resource completes. If not specified, the file specified by this RunList is retained indefinitely. RunList / LayoutElement / FileSpec / Disposition takes precedence over RunList / Disposition . Modification note: starting with JDF 1.4, “this RunList ” above replaces “this FileSpec ”. |
||
|
Replacement text for a DynamicField Element. This information defines the contents of a dynamic mark on the automated page layout (see Section 7.2.109.10.1, “Dynamic Marks”). The mark must be filled using information from the document RunList , (e.g., the bar code of the recipient). This information varies with the document content. DynamicInput Elements have one optional Name Attribute that, when linked to the ReplaceField Attribute of the DynamicField Element, defines the string that is to be replaced. Deprecation note: starting with JDF 1.4, metadata should be extracted from the PDL itself or from other sources, but not from the RunList . DynamicInput was designed to associates metadata with RunList Elements. |
||
|
Describes how Sheets and Surfaces are to be completed and optional media which may be inserted at the beginning or end of this RunList Resource. |
||
|
Represents the results of the PDL interpretation Process. At most one of ByteMap , InterpretedPDLData or LayoutElement must be specified. If none of ByteMap , InterpretedPDLData or LayoutElement are specified, the RunList specifies empty content. |
||
|
Describes the document, finished page or image. At most one of ByteMap , InterpretedPDLData or LayoutElement must be specified. If none of ByteMap , InterpretedPDLData or LayoutElement are specified, the RunList specifies empty content. |
||
|
Describes the mapping of Metadata in a RunList to PartIDKeys |
||
|
PageList ? |
Specification of page metadata for pages described by this RunList . |
Example 7-48: Marks and Reordering of Content using RunList/@IgnoreContext
Assume that a VDP job consists of sets where each set contains a Cover Letter, Brochure, and Postcard document types. Production needs all of each document type for all sets printed first, and the imposition includes dynamic marks where some of the marking uses SheetIndex . The RunListLink parameterizes the processing such that all Cover Letter sheets for all sets are processed first, followed by the Brochure sheets for all sets, and finally, the Postcard sheets for all sets. The RunList then specifies @ IgnoreContext = "SheetIndex" , which forces the SheetIndex to be calculated in the order in which sheets are produced by the processing of the reordered “virtual” RunList .
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< RunList Class = "Parameter" ID = "MyVDPRunList" Status = "Available"
PartIDKeys = "DocTags" IgnoreContext = "SheetIndex" >
<!-- additional attributes and elements -->
< RunList DocTags = "CoverLetter" />
< RunList DocTags = "Brochure" />
< RunList DocTags = "Postcard" />
< RunListLink Usage = "Input" rRef = "MyVDPRunList" >
< Part DocTags = "CoverLetter" />
< Part DocTags = "Brochure" />
< Part DocTags = "Postcard" />
To enable later reprinting of part of the RunList , the RunList then might also specify a MetadataMap Element that extracts the value of a RecordNumber metadata key and assigns the value to Metadata0 . Subsequently, if record # 12 needs reprinting, the RunListLink can be modified to appear as:
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<RunList Class="Parameter" ID="MyVDPRunList" Status="Available"
PartIDKeys="DocTags" IgnoreContext="SheetIndex" >
<!-- additional attributes and elements -->
<RunList DocTags="CoverLetter"/>
< RunListLink Usage = "Input" rRef = "MyVDPRunList" ProcessUsage = "Document" >
< Part DocTags = "CoverLetter" Metadata0 = "12" />
< Part DocTags = "Brochure" Metadata0 = "12" />
< Part DocTags = "Postcard" Metadata0 = "12" />
7.2.160.1 Element: DynamicInput
|
Label that must match the ReplaceField Attribute of the appropriate DynamicField Element |
||
|
Defines the text string that is to be inserted as a replacement for the text defined in ReplaceField of a DynamicField Element. |
7.2.160.2 Element: MetadataMap
The MetadataMap in RunList allows metadata embedded in PDL files to be assigned to Partition Key values, certain RunList Attributes, or Attributes created using GeneralID . During the mapping of PDL data to the JDF document structure (see the definition in the glossary or the discussion in the Imposition Process), each MetadataMap Element will be evaluated for each node (Set, Document, Page, etc.) of the PDL document structure. For XML based PDL files an XPath expression will be evaluated relative to the XML node that defines each node in the document hierarchy. For non-XML based PDLs a PDL specific mapping of the XPath to the PDL document structure is used instead and the value assignment is performed on the derived XML for the PDL file. If the path specified by the XPath does not exist in the PDL, then the associated metadata value is undefined, otherwise the metadata value will be set to the conversion of the node list to a string.
|
Specifies the node context in which the XPaths specified in this MetadataMap Element are to be evaluated. Set - evaluated relative to the current set node. Document - evaluated relative to the current document node. SubDoc0 - evaluated relative to the current subdocument immediately below the Document level. SubDoc1 - evaluated relative to the current subdocument immediately below SubDoc0 level. SubDoc2 - see SubDoc1 , but relative to SubDoc1 level. SubDoc3 - see SubDoc1 , but relative to SubDoc2 level. SubDoc4 - see SubDoc1 , but relative to SubDoc3 level. SubDoc5 - see SubDoc1 , but relative to SubDoc4 level. SubDoc6 - see SubDoc1 , but relative to SubDoc5 level. SubDoc7 - see SubDoc1 , but relative to SubDoc6 level. SubDoc8 - see SubDoc1 , but relative to SubDoc7 level. SubDoc9 - see SubDoc1 , but relative to SubDoc8 level. Object - evaluated for each unique object on each page. PagePool - evaluated relative to the current Page Pool . |
||
|
Expected data type of the metadata value. PartIDKeys - with this value, @ Name MUST match a Partition Key. Values are also from: GeneralID /@ DataType . |
||
|
If DataType = "PartIDKeys" , the value of Name MUST be a PartIDKeys value. See @ PartIDKeys in Table 3-27, “Partitionable Resource Element”.
If
Name
=
"ObjectTags"
, then values are added to a logical pool of tag values associated with each object being processed. This pool of object tags is referenced from:
ColorSpaceConversionParams
/
ColorSpaceConversionOp
/@
ObjectTags
,
ScreeningParams
/
ScreenSelector
/@
ObjectTags
,
ObjectResolution
/@
ObjectTags
, Otherwise, Name specifies the value of an implied variable (e.g. for use in GeneralID /@ IDUsage , RunList /@ EndOfSet , RunList /@ SetCopies , RunList /@ PageCopies , or RunList /@ DocCopies .). If @ DataType is not "PartIDKeys" or a RunList implied variable name (e.g. RunList /@ DocCopies ), then the MetadataMap Element is equivalent to explicitly defining a GeneralID Element with the value being assigned by MetadataMap /@ ValueFormat . The following example counts the number of Page Elements within all DocPart Elements. < MetadataMap DataType = "Integer" Name = "NumPages" ValueFormat = "%d" ValueTemplate = "npages" > Path = "count(../DocPart/Page)" > If multiple MetadataMap Elements specify the same name, then the specified key has the value from the last MetadataMap Element to assign a value to that key. If the specified Name sets the value for a PartIDKeys or RunList variable, where a RunList Attribute also supplies a value (e.g. RunList /@ RunTag , RunList /@ DocCopies , ...), the value supplied by the RunList Attribute shall be replaced by the value supplied by the MetadataMap . |
||
|
Formatting value for combining extracted values from the Expr Elements. Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
Arguments for combining extracted values from the Expr Elements. The argument names MUST match the values of Expr /@ Name . Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
Expr + |
Each Expr Element describes a Term expression (see Section 7.3.13, “Term”and Section 7.3, “Device Capability Definitions”) evaluating metadata values in the PDL. If Expr / Term is not specified, or if the Term expression returns true, then the value specified by the Expr element is assigned to the key specified by MetadataMap /@ Name . Expr Elements are evaluated in the XML order specified. Expr Elements with identical @ Name Attributes where a previous Expr Element with that @ Name has already evaluated to true MUST NOT be processed. If any name specified in MetadataMap /@ ValueTemplate is unassigned, then the key specified by MetadataMap /@ Name is undefined. |
7.2.160.3 Element: Expr
|
Name of this Expr . The value (as specified by @ Value or extracted from @ Path ) MUST be used to evaluate the parent @ ValueTemplate . |
||
|
If specified, and either the value returned by the Term Element (if present) is true or no Term Element is specified, then the value specified by this path is assigned to Expr /@ Name . If the Path does not evaluate to a value, then this Expr Element fails and any subsequent Expr Elements are evaluated. Constraint: exactly one of Path or Value MUST be specified in an Expr Element. |
||
|
If specified, and either the value returned by the Term Element (if present) is true or no Term Element is specified, then the value of this Attribute is assigned to Expr /@ Name . Constraint: exactly one of Path or Value MUST be specified in an Expr element. |
||
|
Term ? |
Evaluates one or more metadata values from the PDL, and returns a true or false result. Evaluation/@XPath MUST be specified for all Evaluation Elements in the Term hierarchy. |
For PPML the XPath expression will be relative to the JOB, DOCUMENT or PAGE element. Example XPath expressions:
- “METADATA/DATUM[@key="Gender"]” will extract the value of the Gender metadata for each JDF set, document and page.
- “count(PAGE)” will count the pages within a given document (only works for JDF document level Nodes).
- “count(PAGE/METADATA/DATUM[@key="special"])” will count the number of pages that have a Special metadata defined for it.
MetadataMap may also be used to set the value of certain RunList Attributes. These Attributes are EndOfSet , EndOfDocument , PageCopies , DocCopies and SetCopies . The values set will be instantiated as if actually present in a Partitioned RunList for the current page or Page Pool being processed. Care should be taken to ensure their consistency across Page Pools within a document or set.
Example 7-49: MetadataMap: Setting Attributes
This example extracts the value of the Copies Attribute as specified by the Path , and sets the value of RunList /@ DocCopies .
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<RunList Class="Parameter" ID="r000004" Status="Available">
< MetadataMap DataType = "Integer" Name = "DocCopies" ValueFormat = "%d"
< Expr Name = "ncopies" Path = "//record/document/@Copies" />
< Expr Name = "ncopies" Value = "1" />
Example 7-50: RunList/MetadataMap
In the following example, the MetadataMap Element maps arbitrary tags in the document to a structural RunTag Partition Key. Note that any Partition Key may be mapped. Note also that although an XPath syntax is used, this may be mapped to any hierarchical structure including but not limited to XML. Finally, note that if / Dokument /@ Sektion is a value other than "Einband" or "HauptTeil" , then the Expr Elements assigning values to section will all fail, resulting in RunTags being undefined.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<!--this runlist points to a structured pdl with arbitrary structural
< RunList Class = "Parameter" ID = "r000004" Status = "Available" >
< MetadataMap DataType = "PartIDKey" Name = "RunTags"
ValueFormat = "%s%s" ValueTemplate = "sex,section" >
<!--This expression maps the value of /Dokument/Rezipient/@Sex
< Expr Name = "sex" Path = "/Dokument/Rezipient/@Sex" />
<!--Maps all elements with /Dokument/@Sektion=Einband to Cover-->
< Expr Name = "section" Value = "Cover" >
< NameEvaluation Path = "/Dokument/@Sektion" RegExp = "Einband" />
<!--Maps all elements with /Dokument/@Sektion=HauptTeil and >50 pages
< Expr Name = "section" Value = "BigBody" >
< NameEvaluation Path = "/Dokument/@Sektion" RegExp = "HauptTeil" />
< IntegerEvaluation Path = "count(PAGE)" ValueList = "51 ~ INF" />
<!--Maps all elements with /Dokument/Sektion=HauptTeil and <=50 pages
< Expr Name = "section" Value = "SmallBody" >
< NameEvaluation Path = "/Dokument/Sektion" RegExp = "HauptTeil" />
< IntegerEvaluation Path = "count(PAGE)" ValueList = "0 ~ 50" />
< LayoutElement Class = "Parameter" >
< FileSpec Class = "Parameter"
MimeType = "application/vnd.foobar+xml" URL = "bigVariable.foo" />
<!--Layout for versioned product-->
< Layout Class = "Parameter" ID = "r000005" PartIDKeys = "RunTags" Status = "Available" >
< Layout RunTags = "MaleCover" >
< Part RunTags = "MaleCover" />
< Layout RunTags = "FemaleCover" >
< Part RunTags = "FemaleCover" />
< Layout RunTags = "MaleBigBody FemaleBigBody" >
< Part RunTags = "MaleBigBody MaleSmallBody FemaleBigBody
< Layout RunTags = "MaleSmallBody FemaleSmallBody" >
< Part RunTags = "MaleBigBody MaleSmallBody FemaleBigBody
< Media Class = "Consumable" ID = "r000006" PartIDKeys = "RunTags"
PartUsage = "Implicit" Status = "Available" >
< Media RunTags = "MaleCover" />
< Media RunTags = "FemaleCover" />
< Media RunTags = "MaleBigBody MaleSmallBody FemaleBigBody FemaleSmallBody" />
<RunListLink Usage="Input" rRef="r000004"/>
<LayoutLink Usage="Input" rRef="r000005"/>
Example 7-51: RunList: Unstructured Single-File RunList
The following five examples illustrate how a RunList can be structured using Partitioning mechanisms. Note that the Partitioning of a RunList often generates the values necessary to evaluate the Partitioning of other Resources, (e.g., the RunIndex into the RunList ). Thus, the order in which the RunList Elements appear in the XML document is significant. Note that the Run Partition Key has a string value, which may be non-numeric. Below is an example of simple unstructured single-file RunList . This example specifies all pages contained in "/in/colortest.pdf" .
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< RunList Class = "Parameter" ID = "Link0003" Pages = "0 ~ -1" Status = "Available" >
< FileSpec URL = "File:///in/colortest.pdf" />
Example 7-52: RunList: Multi-File Unseparated RunList
Example of simple multi-file unseparated RunList using RunList /@ Directory . This example specifies all pages contained in File1.pdf and File2.pdf, which are located in the directory "///Dir/" that is specified in RunList /@ Directory .
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< RunList Class = "Parameter" Directory = "File:///Dir/" ID = "Link0003"
PartIDKeys = "Run" Status = "Available" >
< RunList Pages = "0 ~ -1" Run = "1" >
< FileSpec URL = "File1.pdf" />
< RunList Pages = "0 ~ -1" Run = "2" >
< FileSpec URL = "File2.pdf" />
Example 7-53: RunList: Multi-File Unseparated RunList with Spawning
Example of simple multi-file unseparated RunList with independent spawning. This example specifies the first five pages contained in File1.pdf and File2.pdf. File2.pdf has been spawned and is being processed individually.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< RunList Class = "Parameter" ID = "Link0003" PartIDKeys = "Run" Status = "Available" >
< RunList Pages = "0 ~ 4" Run = "1" >
< FileSpec URL = "File:///File1.pdf" />
< RunList Pages = "0 ~ -1" Run = "2" SpawnStatus = "SpawnedRW" >
< FileSpec URL = "File:///File2.pdf" />
Example 7-54: RunList: Spawned RunList
This is the corresponding spawned RunList . Note the LogicalPage Attribute, which specifies the number of skipped pages.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< RunList Class = "Parameter" ID = "Link0003" LogicalPage = "5" Pages = "0 ~ -1"
PartIDKeys = "Run" Status = "Available" >
< FileSpec URL = "File:///File2.pdf" />
Example 7-55: RunList: Multi-File Separated RunList
This example specifies all pages contained in Presep.pdf and following that, pages 1, 3 and 5 of each preseparated file.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
< RunList Class = "Parameter" ID = "Link0003" PartIDKeys = "Run Separation"
< RunList Run = "1" SkipPage = "3" >
< FileSpec URL = "File:///Presep.pdf" />
< RunList FirstPage = "0" IsPage = "false" Separation = "Cyan" />
< RunList FirstPage = "1" IsPage = "false" Separation = "Magenta" />
< RunList FirstPage = "2" IsPage = "false" Separation = "Yellow" />
< RunList FirstPage = "3" IsPage = "false" Separation = "Black" />
< RunList IsPage = "true" Pages = "1 3 5" Run = "2" >
< RunList IsPage = "false" Separation = "Cyan" >
< FileSpec URL = "File:///Cyan2.pdf" />
< RunList IsPage = "false" Separation = "Magenta" >
< FileSpec URL = "File:///Magenta2.pdf" />
< RunList IsPage = "false" Separation = "Yellow" >
< FileSpec URL = "File:///Yellow2.pdf" />
< RunList IsPage = "false" Separation = "Black" >
< FileSpec URL = "File:///Black2.pdf" />
<RunListLink Usage="Input" rRef="Link0003"/>
7.2.161 SaddleStitchingParams
See Section P.4.13, “SaddleStitchingParams” for details of this deprecated Resource.
7.2.162 ScanParams
This Resource provides the parameters for the Scanning Process.
ArtDeliveryIntent / ArtDelivery
|
Specifies the compression filter to be used. CCITTFaxEncode - Used to select CCITT Group 3 or 4 facsimile encoding. DCTEncode - Used to select JPEG compression. FlateEncode - Used to select Zip compression. |
||
|
A value between 0 and 1 that indicates “how much” the Process is to compress images. 0.0 means “do as loss-less compression as possible.” 1.0 means “do the maximum compression possible.” |
||
|
Rectangle that describes the image section to be scanned, in points. The origin of the coordinate system is the lower left corner of the physical item to be scanned. |
||
|
ID of the drum or other mounting Device upon which the media is to be mounted. |
||
|
Specifies how to mount originals. Unfixed - Original lies unfixed on the scanner tray/drum. Fixed - Original is fixed on the scanner tray/drum with transparent tape. Wet - Original is put in gel or oil and fixed on the scanner tray/drum. Registered - Original is fixed with registration holes. This value is used for copy dot scans. |
||
|
A number representing how many images are scanned before a new file is created. |
||
|
FileSpec ( CorrectionProfile ) ? |
A FileSpec Resource pointing to an ICC profile that describes color corrections. |
|
|
FileSpec ( TargetProfile ) ? |
A FileSpec Resource pointing to an ICC profile that defines the target output Device for a Device specific scan, (e.g., the profile of a CMYK press). |
|
|
FileSpec ( ScanProfile ) ? |
A FileSpec Resource pointing to an ICC profile that describes the scanner. |
7.2.163 ScavengerArea
This Resource describes a scavenger area for removing excess ink from printed Sheets. It is defined within a MarkObject of a surface.
|
Position of the center of the scavenger area in the coordinates of the MarkObject that contains this mark. |
||
|
Rotation in degrees. Positive graduation figures indicate counter-clockwise rotation; negative figures indicate clockwise rotation. |
||
7.2.164 ScreeningParams
This Resource specifies the parameter of the Screening Process. Since screening is, in most cases, very OEM specific, the following parameters are generic enough that they can be mapped onto a number of OEM controls.
ContactCopyParams , ContentList / ContentData , ExposedMedia , LayoutElement , PageList , PageList / PageData
Separation , SheetName , Side , SignatureName
ContoneCalibration , Screening
|
Specifies whether to ignore the screen settings (e.g., setscreen, setcolorscreen and sethalftone) specified in the source files. Note that in some cases, halftones are used to create patterns. In these cases, the halftone in the source PDL file will not be overridden. |
||
|
Specifies what happens when the Device can not fulfill the screening requests. If "true" , it flushes the Job. If "false" , it ignores matching errors using the default screening. Use SettingsPolicy in JDF 1.2 and beyond. |
||
|
List of screen selectors. A screen selector is included for each separation, including a default specification. ScreenSelector MUST contain the complete set of Parameters for a given screening operation. For instance, it is invalid to specify one ScreenSelector for a given @ ObjectTags and another ScreenSelector for a given @ SourceObjects . |
7.2.164.1 Element: ScreenSelector
Description of screening for a selection of source object types and separations.
|
Specifies the first angle of the screen when AM screening is used, otherwise Angle is ignored. At most one of Angle or AngleMap must be specified. If neither Angle nor AngleMap are specified, the angle is determined by the default of the selected ScreeningFamily . |
||
|
Specifies the mapping of the angle of the screen to the angle of a different separation when AM screening is used. For example, a spot color that has the same screening angle as the cyan separation is specified by AngleMap = "Cyan" . In FM screening, AngleMap specifies the mapping of the separation specific screen functions, (e.g., threshold arrays). At most one of Angle or AngleMap must be specified. This mapping is not transitive, so, when Separation already specifies a color with a known default, it specifies the angle of the separation defined by AngleMap prior to that separation being mapped. Note that, in general, the known default will be a CMYK process color, but it can also be another process color, (e.g., HexaChrome™). The following example specifies that Black is to be mapped to the Cyan default separation and Cyan to the Black default separation. The third line maps Spot1 to Magenta. < ScreenSelector AngleMap = "Black" Separation = "Cyan" /> < ScreenSelector AngleMap = "Cyan" Separation = "Black" /> < ScreenSelector AngleMap = "Magenta" Separation = "Spot1" /> |
||
|
Specifies the dot size of the screen, in microns [m], when FM screening ( ScreeningType = "FM" or "Adaptive" ) is used, otherwise DotSize is ignored. |
||
|
Specifies the halftone screen frequency in lines per inch (lpi) of the screen when AM screening is used, otherwise Frequency is ignored. With some screens, frequency can change as a function of gray level. In this case, the Frequency value is interpreted for a midtone (50%) gray level. If Frequency is not specified, the frequency is determined by the default of the selected ScreeningFamily . |
||
|
Tags associated with individual objects that this ScreenSelector MUST be applied to. Each tag specified in ObjectTags is logically anded with the object type(s) specified by SourceObjects , enabling first qualification by object type (such as image), and then tags associated with those objects. The values of ObjectTags depends on the PDL that the ScreenSelector is applied to. |
||
|
Vendor specific screening family name. Sample values removed in JDF 1.2 |
||
|
AM - Can be line or dot. (See SpotFunction .) |
||
|
The name of the separation. If Separation = "All" , the ScreenSelector is to be applied to all separations that are not specified explicitly. |
||
|
Specifies the line frequency of screens which is to be matched from the source file when screen matching is to be done. Note that this is a filter that selects on which objects to apply this ScreenSelector . |
||
|
Identifies the class(es) of incoming graphical objects on which to use the selected screen. ImagePhotographic - Contone images. ImageScreenShot - Images largely comprised of rasterized vector art. LineArt - Vector objects other than text. |
||
|
Specifies the spot function of the screen when AM screening is used. In general, it is common for a spot function to change its shape as a function of gray level. Response to these spot function names may be implementation-dependent. These example names are the same as the spot function names defined in PDF. |
7.2.165 SeparationControlParams
This Resource provides the controls needed to separate composite color files.
7.2.166 SeparationSpec
This Resource specifies a specific separation, and is usually used to define a list or sequence of separations.
ColorIntent / ColorsUsed , NumberingIntent / NumberItem , ProofingIntent / ProofItem , ColorantAlias , ColorantControl / ColorantConvertProcess , ColorantControl / ColorantOrder , ColorantControl / ColorantParams , ColorantControl / DeviceColorantOrder , ColorantControl / ColorSpaceSubstitute , ColorControlStrip , ColorSpaceConversionOp , ContentList / ContentData , DeviceNSpace , LayoutElement , PageList , PageList / PageData , RegisterMark , ScavengerArea , TrappingDetails / TrappingOrder
|
Name of one specific separation. If Name is not specified, this SeparationSpec consumes a slot in a separation order without setting a separation, for instance when specifying modules to skip on a press or color fields to leave blank in a ColorControlStrip . |
7.2.167 Shape
|
If "true" , the inside of a specified shape will be removed. If "false" , the outside of a specified shape will be removed. An example of an inside shape is a window. An example of an outside shape is a shaped greeting card. |
||
|
Specification of a complex path. This may be an open path in the case of a single line. |
||
|
Type of cut or perforation used. Perforate - Interrupted perforation that does not span the entire Sheet |
||
|
Type of cut or perforation used. a number between "0" and "999" corresponding to a line type as defined in DDES3 standard (ANSI® IT8.6-2002). |
||
|
Transparent material that fills a shape (e.g., an envelope window) that was cut out when CutOut = "true" . |
||
|
Depth of the shape cut, measured in microns [m]. If not specified, the shape is completely cut. |
||
|
Describes any precision cutting other than hole making. RoundedRectangle - Rectangle with rounded corners. New in JDF 1.3 |
||
|
The name of the 1-up design in the die layout. Used to match DieLayout / Station Elements with Shape Elements. |
||
|
Number of teeth in a given perforation extent, in teeth/point. MicroPerforation is defined by specifying a large number of teeth (n > 1000). |
7.2.168 ShapeCuttingParams
ShapeCuttingParams defines the details of the ShapeCutting Process.
|
FullSheet - The output of the die-cutter are complete Sheets. The blanks are kept in place with nicks. Front waste (gripper margin) has not been removed. RemoveGripperMargin - The output of the die-cutter are complete Sheets. The blanks are kept in place with nicks. Front waste (gripper margin) has been removed. SeparateBlanks - The output of the die-cutter are blanks that have been removed from the Sheets. |
||
|
Lay of input media. Reference edge of where paper is placed in the feeder. |
||
|
A Resource containing the reference of an external file describing the cutting and other paths. |
||
|
Shape * |
7.2.169 ShapeDef
A structural design describing a 2D surface with paths that describe different finishing operations like cutting, creasing, perforation, etc. In the case of box production this resource is a description of the unprinted blank box as it will be available after die cutting and blanking and before folding. A ShapeDef is defined either by an external file ( FileSpec ) describing the structural design or a collection of PDFPaths contained in Shape elements. In case this description is stored in a file, the format of this file may be a vendor specific format, a standard DDES3 file (ANSI® IT8.6-2002), or less well specified but commonly used formats like CFF2 or DXF or even a PDF or EPS file.
DieLayout / Station , LayoutElementProductionParams
|
A rectangle describing the bounding box of all cut lines. This is sometimes referred to as the knife to knife dimensions of the BlankBox. This Attribute is usually only valid after the generation of the structural design. |
||
|
Width x, height y and depth z coordinates of the 3D shape. For a box, these are the outer dimensions e.g. for palletizing. |
||
|
Intended direction of the flute for this design in the coordinate system defined by CutBox . This information needs to be taken into account by the DieLayoutProduction Process to give the ShapeDef the correct orientation on the Media . XDirection - Along the X-axis of the CutBox coordinate system. YDirection - Along the Y-axis of the CutBox coordinate system. |
||
|
Intended direction of the grain for this design in the coordinate system defined by CutBox . This information needs to be taken into account by the DieLayoutProduction Process to give the ShapeDef the correct orientation on the Media . XDirection - Along the X-axis of the CutBox coordinate system. YDirection - Along the Y-axis of the CutBox coordinate system. |
||
|
Determines the printing side for which the structural design is made. Front - for a box this corresponds to the outside of a box. Back - for a box this corresponds to the inside of a box. Note: folding carton is usually cut from the outside (Front), corrugated from the inside (Back). |
||
|
FileSpec ? |
The FileSpec of the structural design file. The format of this file may be a vendor specific format, a standard DDES3 file (ANSI® IT8.6-2002), less well specified but commonly used formats like CFF2 or DXF or even a PDF or EPS file. FileSpec and Shape are mutually exclusive |
|
|
Media ? |
Media for which this structural design was intended for. The Media description defines important design parameters as the type of Media , thickness, inside loss, outside gain, etc. Media /@ GrainDirection and Media /@ FluteDirection do not have any significance. |
|
|
Shape * |
The shape is defined by a collection of Shape Elements. Shape and FileSpec are mutually exclusive. |
7.2.170 ShapeDefProductionParams
Parameters for the structural design.
7.2.170.1 Element: ObjectModel
|
Width x, height y and depth z values for the bounding box of the object. |
||
|
FileSpec ? |
The FileSpec of the 3D model of the objects that needs to be packed. The format of this file may be a vendor specific format or a standard 3D format like VRML or PDF (U3D). |
7.2.170.2 Element: ShapeTemplate
Additional parametric values MUST be specified with GeneralID Elements. GeneralID /@ IDUsage MUST be set to the name of the Parameter. GeneralID /@ DataType MUST be set to "double" . GeneralID /@ IDValue MUST be set to value of the Parameter.
|
Width x, height y and depth z coordinates of the 3D shape. For a box these are the inner dimensions. |
||
|
The name of the standard this template belongs to e.g. FEFCO, ECMA or the name of a company internal standard. |
||
|
FileSpec ? |
The FileSpec of the parametric structural design. |
The three Figures below show shapes specified by a ShapeTemplate with each named variable represented by a GeneralID that specifies the name and value of the variable. The ShapeTemplate for the diagram below might be:
Example 7-56: ShapeTemplate for Figure 7-53
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<ShapeDefProductionParams Class="Parameter" ID="Link0003"
< GeneralID IDUsage = "L" DataType = "double" IDValue = "1440.0" />
< GeneralID IDUsage = "W" DataType = "double" IDValue = "720.0" />
< GeneralID IDUsage = "D" DataType = "double" IDValue = "1440.0" />
<ShapeDefProductionParamsLink Usage="Input" rRef="Link0003"/>
|
|
|
7.2.171 Sheet
This Resource provides a description of a Sheet, as well as the marks on that Sheet. In JDF 1.3 and beyond, a Sheet is represented as a Layout Partition, namely Layout [@ SheetName ]. For details, see Section 7.2.109, “Layout” .
7.2.172 ShrinkingParams
This Resource provides the parameters for the Shrinking Process in shrink wrapping.
7.2.173 SideSewingParams
See Section P.4.15, “SideSewingParams” for details of this deprecated Resource.
7.2.174 SpinePreparationParams
SpinePreparationParams describes the preparation of the spine of book blocks for hard and soft cover book production, (e.g., milling and notching).
|
Flex quality parameter, in [N/cm]. In JDF 1.2 and beyond, FlexValue is defined in QualityControlParams / BindingQualityParams . See Section 7.2.150, “QualityControlParams” for details. |
||
|
Milling depth, in points. This describes the total cut-off of the spine, regardless of the technology used to achieve this goal. |
||
|
Notching depth relative to the leveled spine, in points. If not specified, there is no notching. |
||
|
List of operations to be applied to the spine. Duplicate entries are allowed to specify a sequence of identical operations. The order of operations is significant. Values include those from: Table 7-358, “Operations Attribute Values”. |
||
|
Pull out quality parameter, in [N/cm]. In JDF 1.2 and beyond, PullOutValue is defined in QualityControlParams / BindingQualityParams . See Section 7.2.150, “QualityControlParams” for details. |
||
|
Starting position of milling tool along the Y-axis of the operation coordinate system. |
||
|
Working length of milling operation. If specified larger than the spine length, the complete spine is prepared. If not specified, the complete spine is prepared. |
-- Attribute: Operations
7.2.175 SpineTapingParams
SpineTapingParams define the parameters for taping a strip tape or kraft paper to the spine of a book block.
7.2.176 StackingParams
Settings for the Stacking Process. A stack of components might be uneven and unstable, due to variations in thickness across each component. The thickness variations might be caused by folding, binding or inserted components. A stack might be split into layers, with successive layers rotated by 180o to compensate for the unevenness (Figure 7-58).
|
If the thickest part is on an edge (e.g., a book binding), the components might be offset to separate the thick parts. Layer compensation and offsetting can be combined as in the following examples of pile patterns (Figure 7-59).
|
If the number of components is not evenly divisible by standard stack size ( StandardAmount ) or the number of components in a bundle is not evenly divisible by layer size ( LayerAmount ), there will be a remainder, yielding one or more odd-count stacks or layers. By default, the odd-count stack or layer size can contain as few as one component. This might exceed equipment cycle times, and flimsy components (newspapers) might cause problems with downstream equipment such as strappers. The MinAmount and MaxAmount control the minimum and maximum size of odd-count stacks and layers. The following figures show the odd count handling for bundles and layers.
|
|
|
In case of nested bundles with BundleType = "Stack" , this parameter addresses the Element to be consumed within the “tree” of such bundles to allow a level of de-stacking. If the real bundle depth level ( BundleType = "Stack" ) is smaller than the value of BundleDepth , individual stack items (i.e., the smallest available level) shall be consumed. If the Input Component referenced does not contain bundles, then this parameter is ignored. BundleDepth = "0" addresses the entire Component , BundleDepth = "1" addresses the bundle in the Component and so on. |
||
|
180 degree rotation applied to successive layers to compensate for uneven stacking. If LayerAmount = StandardAmount , there is one layer, and effectively no compensation. |
||
|
Ordered number of products in a layer. The first number is the first LayerAmount , etc. If there are more layers than entries in the list, counting restarts at the first entry. The sum of all entries is typically an even divisor of StandardAmount . When not known, the default case is that the value of LayerAmount be equivalent to the value of StandardAmount . |
||
|
Maximum number of products in a stack, MaxAmount >= StandardAmount . When not known, the default case is that the value of MaxAmount be equivalent to the value of StandardAmount . |
||
|
Minimum number of products in a stack or layer, ( MaxAmount - StandardAmount ) <= MinAmount < StandardAmount and MinAmount < LayerAmount . Where not known, the default case is to use a value equivalent to MaxAmount - StandardAmount . |
||
|
Offset or shift applied to successive layers to separate the thicker portions of components, for example, offsetting the spines of hardcover books. Replaced with Disjointing in JDF 1.2 and beyond. |
||
|
All - all layers are pre-stacked |
||
|
Number of underlay Sheets at each layer. The first value is underneath the bottom layer, the next value above the bottom layer and so forth. If more layers than values are specified, counting restarts at the 0 position of UnderLays . If less layers than values are specified, all underlay Sheets that are not adjacent to a layer are ignored. |
||
|
Details of the offset or shift applied to successive layers to separate the thicker portions of components, for example, offsetting the spines of hardcover books. |
7.2.177 StaticBlockingParams
StaticBlockingParams defines the details of StaticBlocking .
7.2.178 StitchingParams
This Resource provides the parameters for the Stitching Process. The process coordinate system is defined as follows:
- The Y-axis increases from the (first) registered edge to the edge opposite to the registered edge.
- The X-axis is aligned with the (second) registered edge, and it increases from the binding edge (or first registered edge) to the edge opposite to the binding edge (or first registered edge).
Note that the stitches are applied from the front in the figures describing the stitching coordinate system.
|
ProductionRun , SubRun , WebProduct
|
Angle of stitch in degree. The angle increases in a counterclockwise direction. Horizontal = "0" , which means that it is parallel to the X-axis of the operation coordinate system. Defaults to the system-specified value which may vary depending on other Attributes set in this Resource. If StitchType = "Saddle" , Angle must be ignored |
||
|
Number of stitches. If not specified, use the system-specified number of stitches which may vary depending on other Attributes set in this Resource. Use a "0" value to use the stitcher without inserting any stitches. Use "NoOp" to bypass the stitcher altogether. |
||
|
The edge or corner of the component to be stitched for the process coordinate system (see description above). This Attribute is intended for use when the Stitching Process is part of a Combined Process with other Processes (e.g., DigitalPrinting ) where, when combined, there is no input Component to be stitched. Deprecation note: starting with JDF 1.2, use an explicit Transformation or Orientation of the input Component . If both Transformation / Orientation and ReferenceEdge are specified, the result is the matrix product of both transformations. Transformation / Orientation must be applied first. |
||
|
Distance between stitch and binding edge. If StitchType = "Saddle" , Offset must be ignored. Note that it is possible to describe saddle stitching with an offset by defining StitchType = "Side" with a large Offset value. |
||
|
Specifies the shape of the staples to be used. Note: representations of the values are displayed in Figure 7-62. |
||
|
If "true" , Stitching is done from front to back. Otherwise it is done from back to front. The StitchFromFront has been replaced with an explicit Transformation or Orientation of the input Component . |
||
|
Defines the origin of StitchPositions . For an illustration of the values, see Figure 7-65. |
||
|
Array containing the stitch positions. The center of the stitch must be specified, and the number of entries must match the number given in NumberOfStitches . |
||
|
Specifies the type of the Stitching operation. Corner - Stitch in the corner that is at the clockwise end of the reference edge. For example, to stitch in the upper right corner set ComponentLink /@ Orientation = "Rotate90" . |
||
|
Width of the stitch to be used. If not present or "0" , means use the system-specified width of stitches which may vary depending on other Attributes set in this Resource. |
||
|
Gauge of the wire to be used. If not present or "0" , means use the system-specified wire gauge which may vary depending on other Attributes set in this Resource. |
||
7.2.179 Strap
|
A more specific, specialized or site-defined name for the color. If StrapColorDetails is supplied, StrapColor SHOULD also be supplied. |
||
7.2.180 StrappingParams
StrappingParams defines the details of Strapping .
|
Double - Two parallel single straps. DoubleCross - Two cross straps that strap each side of a box. |
||
|
Positions of the Straps beginning from the origin of the coordinate system (bottom side) increasing from minimum to maximum in points. Each Strap is defined by a 3-tuple of which two values must be 0. The non-zero value specifies the variable coordinate. For instance, two parallel straps shifted along the y-axis are specified as "0 y1 0 0 y2 0" (see Figure 7-66 and Figure 7-67). A centered cross strap in the x-y plane would be specified as "x/2 0 0 0 y/2 0" , which specifies one strap in the x-plane and another in the y-plane. |
|
|
7.2.181 StripBindingParams
This Resource describes the details of the StripBinding Process.
|
The name of the comb manufacturer and the name of the specific item. |
||
|
The distance between the pins and the distance between the holes of the prepunched Sheets must be the same. In JDF 1.2 and beyond, use the value implied by HoleMakingParams /@ HoleType . |
||
|
The length of the pin is determined by the height of the pile of Sheets to be bound. |
||
|
A more specific, specialized or site-defined name for the color. If StripColorDetails is supplied, StripColor SHOULD also be supplied. |
||
|
Details of the holes in StripBinding . |
7.2.182 StrippingParams
The StrippingParams Resource is a high-level description of how a Component is to be produced. It is typically produced by the MIS production planning module and consumed by a prepress workflow system, although its usage is not restricted to this example. There are enough optional Attributes to use the same Resource for the interface between estimation systems and production planning systems.
StrippingParams specifies how the surfaces of the BinderySignature Elements of a Job are placed onto press Sheets and also gives concrete values for the various StripCellParams defined by the BinderySignature .
The Partitioning of StrippingParams defines the structure of the finished product and the structure of the Layout Resource that is produced by the Stripping Process. It is therefore recommended to Partition the StrippingParams Resource by SheetName . Note that some Attributes and Elements must not be specified in the lower level Partitions. For instance, Device and WorkStyle are only useful up to the SheetName Partition level.
SignatureName , SheetName , BinderySignatureName , PartVersion , SectionIndex , CellIndex
|
Identification of the Assembly or AssemblySection to which the StrippingParams or Partition belongs. |
||
|
IDs of the Assembly Elements, AssemblySection Elements or StrippingParams [@ BinderySignatureName ] to which the StrippingParams or Partition belongs. |
||
|
Percentage (1.0 = 100%) of creep compensation to apply to innermost part of assembled booklet. Shingling is perpendicular to the spine. Negative values go towards the spine. Values for pages between inner and outer are interpolated. Actual values of shingling are calculated by the system or operator. See Figure 7-68, “Shingling for Stripping” and Figure 7-69, “Shingling for Stripping - Details”. |
||
|
Identification of the original Job to which the StrippingParams or Partition belongs. If not specified, it defaults to the value specified or implied in the JDF Node. |
||
|
Percentage (1.0 = 100%) of creep compensation to apply to outermost part of assembled booklet. Shingling is perpendicular to the spine. Negative values go towards the spine. Values for pages between inner and outer are interpolated. Actual values of shingling is calculated by the system or operator. See Figure 7-68, “Shingling for Stripping” and Figure 7-69, “Shingling for Stripping - Details”. |
||
|
List of numbered sections (of the AssemblySection Elements with matching JobID and AssemblyIDs ) that are to be flowed into the BinderySignature . If not specified, a linear sequence of sections is assumed. The section that matches the first entry is flowed into SignatureCell Elements with SectionIndex = "0" ; the section that matches the second entry is flowed into SignatureCell Elements with SectionIndex = "1" ; and so forth. SectionList must not be specified at the CellIndex Partition level. |
||
|
Formatting value for identifying individual parts of the Layout . Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
Arguments for combining extracted values for identifying individual parts of the Layout . Values are from: Appendix I, “Generating strings with Format and Template” . |
||
|
If specified, this Attribute describes cut-and-stack imposition. The order of stacks is defined by the order of StrippingParams Partitions. StackDepth MUST NOT be specified in Partitions lower than the Sheet level. |
||
|
The direction in which to turn the press Sheet. Constraint: WorkStyle must not be specified at Partition levels lower than SheetName . |
||
|
Describes BinderySignature which is placed onto the Sheets defined by StrippingParams . If multiple BinderySignature Elements are placed on the same Sheet, StrippingParams must be Partitioned by BinderySignatureName . BinderySignature must not be specified at Partition levels lower than PartVersion . |
||
|
Device * |
Devices that the MIS expects to execute this StrippingParams . This may include prepress Devices, presses or finishing Devices. Press Devices must not be specified at Partition levels lower than SheetName . |
|
|
Reference to an external imposition template in a proprietary format. StrippingParams should not contain information that overlaps information specified in ExternalImpositionTemplate . Information specified in StrippingParams overrides parameters specified in ExternalImpositionTemplate . |
||
|
Media * |
Media to be used for this StrippingParams . This may include paper, plate or film media. Paper media must not be specified at Partition levels lower than SheetName . |
|
|
Position * |
The Position Element specifies how the BinderySignature is placed onto a Sheet. Multiple Position objects in one StrippingParams specify multiple identical BinderySignature Elements with the same content. In case the BinderySignature is defined by SignatureCells, then, by default, the front pages are placed on the front side of the Sheet and the back pages are placed on the back side of the Sheet. Using the Orientation Attribute one can influence this default behavior. When the BinderySignature is defined by FoldCatalog or Fold Elements, then, by default, the lay is placed on the left front side of the Sheet. Using the Orientation Attribute one can influence this default behavior. Position must not be specified at Partition levels lower than PartVersion . |
|
|
Indicates areas on the StrippingParams reserved for Marks. Modification note: Starting with JDF 1.4, the following constraint is removed: a StripMark must not be specified at Partition levels that are more granular than SheetName . |
|
|
7.2.182.1 Element: Position
The Position Element allows the aligned placement of different objects onto a layout, without requiring that the objects be of the same size. The objects are placed onto a display area. The display area includes absolute margins, specified by MarginTop , MarginLeft , MarginRight and MarginBottom . Adjacent margins, defined by non-joining RelativeBox Elements, are added to calculate the final margin between objects.
|
|
Absolute position, in points, of the display area of this BinderySignature or StripMark on the front side of the StrippingParams . The BinderySignature is placed onto the display area after applying the Orientation transformation. The display area includes the absolute margins defined by MarginTop , MarginBottom , MarginLeft and MarginRight . AbsoluteBox overrides RelativeBox if both are specified. |
||
|
Identifies a CutBlock resulting from a Cutting Process if the element specified by the Position is created by Cutting . |
||
|
Bottom margin, in points, to be left outside of the BinderySignature that this Position applies to. The coordinate system is defined by the front side of the StrippingParams . |
||
|
Top margin, in points, to be left outside of the BinderySignature that this Position applies to. The coordinate system is defined by the front side of the StrippingParams . |
||
|
Left margin, in points, to be left outside of the BinderySignature that this Position applies to. The coordinate system is defined by the front side of the StrippingParams . |
||
|
Right margin, in points, to be left outside of the BinderySignature that this Position applies to. The coordinate system is defined by the front side of the StrippingParams . |
||
|
Named orientation describing the transformation of the orientation of the BinderySignature on the StrippingParams . For details, see Table 2-4, “Matrices and Orientation values for describing the orientation of a Component”. |
||
|
Relative position of the display area of this BinderySignature on the front side of the StrippingParams . The BinderySignature is placed onto the display area after applying the Orientation transformation. The display area includes the absolute margins defined by MarginTop , MarginBottom , MarginLeft and MarginRight . AbsoluteBox overrides RelativeBox if both are specified. If neither AbsoluteBox nor RelativeBox are specified, the full relative media box "0 0 1.0 1.0" is applied. |
7.2.182.2 Element: StripCellParams
The StripCellParams allow the specification of various distances implicitly defined by the use of a BinderySignature . The picture below shows a cell and the different distances inside it leading to the final trim box of the cell in which content will be placed.
Note: In practice, StripCellParams values will usually be greater than or equal to zero and have no default.
|
(F2) Value for the trim distance at the face side. When no Folding is done, this is the right margin. When BinderySignatureType = "Grid" , the horizontal gutter between cells is TrimFace + Spine . |
||
|
(S2) Amount of paper which is not cut-off from the spine. When no Folding is done, this is the left margin. When BinderySignatureType = "Grid" , the horizontal gutter between cells is TrimFace + Spine . |
||
|
(H2) Value for the trim distance at the head side. When no Folding is done, this is the top margin. When BinderySignatureType = "Grid" , the vertical gutter between cells is TrimHead + TrimFoot . |
||
|
(T2) Value for the trim distance at the foot side. When no Folding is done, this is the bottom margin. When BinderySignatureType = "Grid" , the vertical gutter between cells is TrimHead + TrimFoot . |
||
|
Compensation for creep. When the creep value is positive, the thickness of the paper is compensated by moving the content pages to the open side of the folded Signature (outer creep). When the creep value is negative, the thickness of the paper is compensated by moving the content pages to the closed side of the folded Signature (inner creep). When the creep value = "0" , then no creep compensation is applied. |
||
|
The definition of the clipping mask for the placed graphics. TrimBox - The mask is derived from the TrimBox as defined by the SignatureCell and StripCellParams . BleedBox - The mask is derived from the BleedBox as defined by the SignatureCell and StripCellParams SourceTrimBox - The mask is derived from the TrimBox of the graphical element placed in the SignatureCell SourceBleedBox - The mask is derived from the BleedBox of the graphical element placed in the SignatureCell . PDL - The mask is derived from the PDL of the graphics. The Attribute MaskSeparation determines which separation is to be used as the clipping mask for the graphics. DieCut - The mask is the cut line as defined in the DieLayout . DieBleed - The mask is the bleed line as defined in the DieLayout . |
||
|
Color /@Name of the separation that specifies Mask . MaskSeparation must be specified if and only if Mask = "PDL" . Color /@ ColorType of this separation must be "DieLine" . |
||
|
Indicates whether contents are to be printed on one or both sides of the media. OneSided - Page contents will only be imaged on one side of the media. TwoSidedHeadToHead - Impose pages upon the front and back sides of media Sheets so that the head (top) of page contents back up to each other. TwoSidedHeadToFoot - Impose pages upon the front and back sides of media Sheets so that the head (top) of the front backs up to the foot (bottom) of the back. |
|
7.2.182.3 Element: StripMark
The StripMark Element specifies Marks to be placed on the Sheet.
|
How to fit the mark in the size. NoRepeat - The mark is neither resized nor repeated horizontally, but it is clipped if it is bigger than size. StretchToFit - The mark is resized horizontally to fill the allocated space. Aspect of the mark may get distorted. UndistortedScaleToFit - The mark is resized to maximum size that can fit in allocated space, without affecting aspect ratio. RepeatToFill - The mark is placed in requested position, then it is repeated horizontally, allowing clipping to occur so that all allocated space is entirely covered. RepeatUnclipped - The mark is placed in requested position, then it is repeated horizontally to fit as much unclipped copies as possible. |
||
|
Used as reference for rRef (mark that is relative to another mark) |
||
|
MarkContext specifies context where a Mark must be applied. MUST NOT specify a MarkContext value that has a higher level than the Partitioning level where StripMark Elements resides Sheet - The mark belongs to a press sheet BinderySignature - The mark belongs to a BinderySignature and must be repeated for each StrippingParams / Position Element. Cell - The mark belongs to a page cell and must be repeated for each pagecell. CellPair - The mark belongs to a bound pair of Sheets repeated for each pair of page cells. |
||
|
MarkName ? |
Mark that is to be marked on the StrippingParams . Values include those from: Table 7-371, “MarkName Attribute Values”. |
|
|
MarkSide ? |
Side and alignment of the marks. Values are from: Table 7-372, “MarkSide Attribute Values”. |
|
|
Position of the Anchor of this StripMark relative to RefAnchor /@ Anchor as defined by @ Anchor , RefAnchor /@ Anchor and @ MarkContext |
||
|
Specifies an index into the Input RunList ( Marks ) for Stripping. |
||
|
Orientation of the mark in the coordinate system of the parent |
||
|
Height relative to the size of the parent specified by @ MarkContext . |
||
|
Width relative to the size of the parent specified by @ MarkContext . |
||
|
More detailed information about the StripMark . If MarkName = "Set" then StripMarkDetails is a name to refer to a private set of marks. |
||
|
How to fit the mark in the size. NoRepeat - The mark is not resized nor repeated vertically, but it is clipped if bigger than size. StretchToFit - The mark is resized vertically to fill the allocated space. Aspect of the mark may get distorted. UndistortedScaleToFit - The mark is placed once, resized to maximum size that can fit in allocated space without affecting aspect ratio. RepeatToFill - The mark is placed in requested position. Then it is repeated vertically, allowing clipping to occur so that all allocated space is entirely covered. If @ HorizontalFitPolicy is set to "RepeatToFill" or "RepeatUnclipped" , horizontal repetition is performed first. Then the resulting row is repeated vertically as requested. RepeatUnclipped - The mark is placed in requested position, then it is repeated vertically to fit as much unclipped copies as possible. If @ HorizontalFitPolicy is set to "RepeatToFill" or "RepeatUnclipped" , horizontal repetition is performed first. Then the resulting row is repeated vertically as requested. |
||
|
Position ? |
Specifies where to place the StripMark on the StrippingParams . Deprecation note: starting with JDF 1.4, the position of the Anchor of this StripMark is relative to RefAnchor /@ Anchor as defined by @ Anchor , RefAnchor /@ Anchor and @ MarkContext |
|
|
JobField ? |
Specific Information about Marks of type JobField . JobField must not be specified unless MarkName = "JobField" . This JobField must not contain a DeviceMark Element. Positioning of the JobField is defined by the Position Element. |
|
|
Details of the coordinate system that this mark is placed relative to. This MAY be either the parent coordinate system or the coordinate system of a referenced StripMark . |
-- Attribute: MarkName
|
Specifies to use a MarkSet (file containing multiple marks). The name of the MarkSet MAY be passed in StripMarkDetails |
|
-- Attribute: MarkSide
|
The Mark is placed on the front side of the surface and Position is specified in the coordinate system of the front surface. |
|
|
The Mark is placed on the back side of the surface and Position is specified in the coordinate system of the back surface. |
|
|
The position of the mark on the back is derived from the position of the mark on the front side and StrippingParams /@ WorkStyle . |
|
|
The Mark is placed on both sides of the surface and the position is specified in the coordinate system of the respective surface. |
7.2.183 Surface
This Resource describes the marks on a Sheet surface. Up to two surfaces can be defined for a Sheet. In JDF 1.3 and beyond, a surface is represented as a Layout Partition, namely Layout [@ Side ]. For details, see Section 7.2.109, “Layout” .
7.2.184 ThreadSealingParams
This Resource provides the parameters for the ThreadSealing Process.
7.2.185 ThreadSewingParams
This Resource provides the parameters for the ThreadSewing Process. It may also specify a gluing application, which would be used principally between the first and the second or the last and the last Sheet but one. A gluing application might also be necessary if different types of paper are used.
The process coordinate system is defined as follows: The Y-axis is aligned with the binding edge. It increases from the registered edge to the edge opposite to the registered edge. The X-axis is aligned with the registered edge. It increases from the binding edge to the edge opposite to the binding edge, (i.e., the product front edge).
|
|
|
A value of "true" specifies a blind stitch after the last stitch. |
||
|
Core material of the thread being used. This Attribute must be used to define the thread material if there is no casting. |
||
|
It contains the indices of the loose parts of the input Component Resources to which gluing is applied. The index starts with 0. GlueLineRefSheets must not be specified unless GlueLine is defined. |
||
|
Specifies the distance between the stitch and the binding edge. Used only for side stitching. |
||
|
Array containing the y-coordinate of the needle positions. The number of entries must match the number specified in NumberOfNeedles . |
||
|
GlueLine * |
7.2.186 Tile
Each Tile Resource defines how content from a surface Resource will be imaged onto a piece of media that is smaller than the designated surface. Tiling occurs in some production environments when pages are imaged on to an intermediate medium, and the resulting image of the surface is larger than the media. In this case, instructions are needed to determine how the intermediate media (tiles) will be assembled to achieve the desired output, (e.g., a single plate for the surface). For example, a Device might require that four pieces of film be assembled to create the image for the plate.
In general, a Tile Resource will be Partitioned (see Section 3.10.5, “Description of Partitioned Resources”) by TileID . Individual tiles are selected and matched by specifying the appropriate TileID Attribute, which is described in Table 3-28, “Part Element”.
|
A rectangle that defines the bounding box of the surface contents which will be imaged on this Tile . The ClipBox is defined in the coordinate system of the surface. |
||
|
A coordinate transformation matrix mapping the ClipBox for this Tile to the rectangle 0 0 X Y, where X and Y are the extents of the media that the Tile will be imaged onto. |
||
|
List of marks that are placed on the tile. MarkObject /@ CTM applies to the coordinate system of the Tile . |
||
|
Media ? |
||
7.2.187 Tool
A Tool Resource defines a generic tool that is customized for needed for a given Job, (e.g., an embossing stamp). The manufacturing process for the tool is not described within JDF.
ArtDeliveryIntent / ArtDelivery , EmbossingParams / Emboss
Any Process , Embossing , ShapeCutting
|
Number of identical instances of the tool that the tool contains, (e.g., the number of cut forms in a die cutting die). Deprecation note: starting with JDF1.3, use DieLayout to describe the number of cut forms in a cutting die. |
||
|
ID of the tool. This is a unique name within the workflow. Replaced by the generic Resource / @ProductID in JDF 1.3 |
||
|
Braille - embossing tool for blind script. New in JDF 1.4 CentralStripper - The center tool of the stripper tool set. Stripping means removing small parts of waste in between blanks. ChangingCuttingBlock - a changeable part for a tool set (CutDie). Used for cutting of optional shapes like windows, stars, etc. It is not a part of tool set. Described in MIS with an own ProductID . New in JDF 1.4 CounterDie - The lower tool of the die-cut pair with the counter (female) parts for the creases CutDie - The upper tool of the die-cut pair with the actual cutting and creasing knifes. FrontWasteSeparator - The tool to remove gripper margin from the Sheet LowerBlanker - The lower tool of the blanker pair (blanking means separating blanks) LowerStripper - The lower tool of the stripper toolset ToolSet - The value "ToolSet" is used when the ToolID refers not to a single tool, but to a set of matching tools (i.e. tool set) that are used in the Process. E.g., when ProductID is a single stock item number in the MIS for a tool set consisting of a CutDie and a CounterDie . |
7.2.188 TransferCurve
TransferCurve Elements specify the characteristic curve of transfer of densities between systems. For more details on transfer curves and their usage, refer to the CIP3 PPF specification at: http://www.cip4.org/documents/technical_info/cip3v3_0.pdf .
Color , Color / PrintConditionColor , TransferCurvePool / TransferCurveSet
RibbonName , SheetName , Side , WebName
7.2.189 TransferCurvePool
A transfer curve pool is a collection of TransferCurveSet Elements that each contains information about a TransferCurve . Multiple TransferCurveSet Elements may exist at one time. For example, one may exist for the laser calibration of the imagesetter, one for the ContactCopying Process and one for the printing Process. Each TransferCurveSet consists of one or more TransferCurve Elements. A TransferCurve Resource is applied to the appropriate Separation , or to all Separation s when Separation = "All" . The TransferCurveSet Elements are concatenated in the following order:
Film -> Plate -> Press -> Paper.
In addition to the TransferCurve Resource, the TransferCurveSet Elements contain Device-dependent geometrical information, (e.g., CTM definitions).
TransferFunctionControl , Layout
ContactCopying , ContoneCalibration , ConventionalPrinting , DigitalPrinting , ImageSetting , InkZoneCalculation , PreviewGeneration , Stripping
7.2.189.1 Element: TransferCurveSet
TransferCurveSet Elements describe both the characteristic curve of transfer and the relation between the various process coordinate systems.
|
Defines the transformation of the coordinate system in the Device as defined by Name . |
||
|
The name of the TransferCurveSet . Film - The transformation from the Layout system to the Film . In a CTP or DigitalPrinting environment, this defaults to the identity matrix and the identity TransferCurve . Plate - The transformation from the Film system to the Plate . In a DigitalPrinting environment, this defaults to the identity matrix and the identity TransferCurve . Press - The transformation from the Plate system to the Press . Paper - The transformation from the Press system to the Paper . Proof - The transformation from the Layout system to the Proof . New in JDF 1.2 |
||
|
List of TransferCurve entries. |
7.2.190 TransferFunctionControl
|
Identifies the source of transfer curves which are to be applied during separation. Custom - Use the transfer curves provided in TransferCurvePool . Device - Use transfer functions provided by the output Device. When Separation is being performed pre-RIP, this can mean that no transfer curves will be applied. Document - Use the transfer curves provided in the document. Modification note: starting with JDF 1.3, the data type changes from enumeration to enumerations. If multiple values are specified, the transfer functions that are specified by the individual enumeration values are concatenated. |
||
|
Provides a set of transfer curves to be used by the Process. |
7.2.191 TrappingDetails
This Resource identifies the root of the hierarchy of Resources. This hierarchy controls the Trapping Process, whether used for PDL or in-RIP trapping.
DocIndex , RunIndex , RunTags, DocTags, PageTags, SetTags, SheetName , Side , SignatureName
|
If "true" , pages that have no defined TrapRegion Elements are trapped using the set of TrimmingParams . The bleed box is used for the trap zone. If "false" , only pages that have TrapRegion Elements are trapped. |
||
|
If "true" , any detectable trapping controls (or traps) provided within any source files used by this Process are ignored. If "false" , trapping controls embedded in the source files are honored. Note that if TrappingDetails (and the Trapping Process) is not present, then the trapping defined in PostScript may still be applied. Deprecation note: starting with JDF1.4, the application of trap annotations is specified in InterpretingParams / PDFInterpretingParams /@ PrintTrapAnnotations. |
||
|
If "true" , trapping is enabled. If "false" , trapping is disabled. Use NoOp in JDF 1.2 and above. |
||
|
Identifies the trapping method to be used by the Trapping Process. The number identifies the minor (last three digits) and major (any digits prior to the last three) version of the trapping type requested. |
||
|
Trapping Processes will trap colorants as if they are laid down on the media in the order specified in TrappingOrder . The colorant order can affect which colors to spread, especially when opaque inks are used. |
||
|
A TrappingParams Resource that is used to define the default trapping parameters when DefaultTrapping = "true" . |
||
|
Elements which define the resolutions to trap the contents at. More than one Element may be used to specify different resolutions for different SourceObjects types. |
||
|
A set of TrapRegion Resources that identify the pages to be trapped, the geometry of the areas to trap on each page, and the trapping settings to use for each area. |
7.2.192 TrappingParams
This Resource provides a set of controls that are used to generate traps. The values of the parameters are chosen based on the customer’s trapping strategy, and depend largely on the content of the pages to be trapped and the characteristics of the output Device (or press).
DocIndex , RunIndex , RunTags , DocTags , PageTags , SetTags , SheetName , Side , SignatureName
|
A number between 0 and 1 that specifies the lowest color value needed for trapping a colorant according to the black trapping rule. This entry uses the subtractive notion of color, where 0 is white or no colorant, and 1 is full colorant. |
||
|
A positive number that specifies the lowest neutral density of a colorant for trapping according to the black trapping rule. |
||
|
A positive number that specifies the trap width for trapping according to the black trapping rule. The BlackWidth is specified in TrapWidth units; a value of "1" means that the black trap width is one TrapWidth wide. The resulting black trap width is subject to the same Device limits as TrapWidth . |
||
|
If "true" , trapping is enabled for zones that are defined with this parameter set. |
||
|
A name that identifies a halftone object to be used when marking traps. The name is the value of the ResourceName Attribute of some PDLResourceAlias Resource . If absent, the halftone in effect just before traps are marked will be used, which may cause unexpected results. |
||
|
If "true" , the planes of color images are trapped against each other. If "false" , the planes of color images are not trapped against each other. |
||
|
A positive integer indicating the minimum resolution, in dpi, for downsampled images. Images can be downsampled by a power of 2 before traps are calculated. The downsampled image is used only for calculating traps, while the original image is used when printing the image. |
||
|
Controls trapping when the TrapZone contains a stencil mask. A stencil mask is a monochrome image in which each sample is represented by a single bit. The stencil mask is used to paint in the current color: image samples with a value of "1" are marked, samples with a value of "0" are not marked. When "false" , none of the objects covered by the clipped bounding box of the stencil mask are trapped. No traps are generated between the stencil mask and objects that the stencil mask overlays. No traps are generated between objects that overlay the stencil mask and the stencil mask. For all other objects, normal trapping rules are followed. Two objects on top of the stencil mask that overlap each other might generate a trap, regardless of the value of this parameter. When "true" , objects are trapped to the stencil mask, and to each other. |
||
|
If "true" , traps are generated along a boundary between images. If "false" , this kind of trapping is not implemented. |
||
|
If "true" , images are trapped to other objects. If "false" , this kind of trapping is not implemented. |
||
|
Controls the placement of traps for images. Center - Trap is centered on the edge between the image and the adjacent object. Choke - Trap is placed in the image. |
||
|
Specifies in points the width of image-to-image, image-to-object and/or image internal non-black traps in X direction (horizontal) of the PDF or ByteMap defined in the input RunList when ImageToImageTrapping, ImageToObjectTrapping and/or ImageInternalTrapping are set to true . The parameter applies only to non-black traps if an image color on either side qualifies as black. The effective black trap width is used to compute the size of the trap. This is based on TrapWidth , BlackWidth and MinimumBlackWidth . Values must be greater than or equal to zero. A value of 0.0 disables non-black image trapping. Defaults to TrapWidth . |
||
|
Specifies in points the width of image-to-image, image-to-object and/or image internal non-black traps in Y direction (vertical) of the PDF or ByteMap defined in the input RunList when ImageToImageTrapping, ImageToObjectTrapping and/or ImageInternalTrapping are set to true . The parameter applies only to non-black traps if an image color on either side qualifies as black. The effective black trap width is used to compute the size of the trap. This is based on TrapWidth , BlackWidth and MinimumBlackWidth . Values must be greater than or equal to zero. A value of 0.0 disables non-black image trapping. Defaults to ImageTrapWidth . |
||
|
Specifies the minimum width, in points, of a trap that uses black ink. Allowable values are those greater than or equal to zero. |
||
|
A number between 0 and 1. Specifies when to slide traps towards a center position. If the neutral density of the lighter area is greater than the neutral density of the darker area multiplied by the SlidingTrapLimit , then the trap slides. This applies to vignettes and non-vignettes. No slide occurs at "1" . |
||
|
A non-negative number. Specifies the smallest step needed in the color value of a colorant to trigger trapping at a given boundary. If the higher color value at the boundary exceeds the lower value by an amount that is equal or greater than the larger of 0.05 or StepLimit times the lower value (low + max ( StepLimit * low, 0.05)), then the edge is a candidate for trapping. The value 0.05 is set to avoid trapping light areas in vignettes. This entry is used when not specified explicitly by a ColorantZoneDetails Subelement for a colorant. The restriction that StepLimit be less than or equal to one (<=1) was removed in JDF 1.2. |
||
|
A number between 0 and 1. Specifies a scaling of the amount of color applied in traps towards the neutral density of the dark area. A value of "1" means the trap has the combined color values of the darker and the lighter area. A value of "0" means the trap colors are reduced so that the trap has the neutral density of the darker area. This entry is used when not specified explicitly by a ColorantZoneDetails Subelement for a colorant. |
||
|
Instructs the trap engine how to form the end of a trap that touches another object. Note: other values might be added later from customer requests. |
||
|
Specifies the style of the connection between the ends of two traps created by consecutive segments along a path. |
||
|
Specifies the trap width, in points in X direction (horizontal) of the PDF or ByteMap defined in the input RunList . Also defines the unit used in trap width specifications for certain types of objects such as BlackWidth . |
||
|
Specifies the trap width, in points in Y direction (vertical). Also defines the unit used in trap width specifications for certain types of objects such as BlackWidth . If not specified, defaults to the value of TrapWidth . |
||
|
ColorantZoneDetails Subelements. Entries in this dictionary reflect the results of any named colorant aliasing specified. Each entry defines parameters specific for one named colorant. If the colorant named is neither listed in the ColorantParams array nor implied by the ProcessColorModel for the ColorantControl object in effect when these TrappingParams are applied, the entry is not used for trapping. |
7.2.192.1 Element: ColorantZoneDetails
|
The colorant name that occurs in the SeparationSpec /@ Name of the ColorantParams array of the ColorantControl object used by the Process. |
||
|
A number between 0 and 1. Specifies the smallest step specified in the color value of a colorant to trigger trapping at a given boundary. If the higher color value at the boundary exceeds the lower value by an amount that is equal or greater than the larger of 0.05 or StepLimit times the lower value (low + max ( StepLimit * low, 0.05)), then the edge is a candidate for trapping. The value 0.05 is set to avoid trapping light areas in vignettes. If omitted, the StepLimit Attribute in the TrappingParams Resource is used. |
||
|
A number between 0 and 1. Specifies a scaling of the amount of color applied in traps towards the neutral density of the dark area. A value of "1" means the trap has the combined color values of the darker and the lighter area. A value of "0" means the trap colors are reduced so that the trap has the neutral density of the darker area. If omitted, the TrapColorScaling Attribute in the TrappingParams Resource is used. |
7.2.193 TrapRegion
This Resource identifies a set of pages to be trapped, an area of the pages to trap, and the parameters to use.
|
Each element within TrapZone is one subpath of a complex path. The TrapZone is the area that results when the paths are filled using the non-zero winding rule. When absent, the MediaBox array for the RunList defines the TrapZone . |
||
|
Identifies a set of pages from the RunList to trap using the specified geometry and trapping style. The logical indices that Pages reference in a RunList are referenced in the same way as Layout / ContentObject /@ Ord does. For details, see Section 7.2.109.12.4, “Using Ord to Reference Elements in RunList Resources”. |
||
|
The set of trapping parameters which will be used when trapping in this region. |
7.2.194 TrimmingParams
This Resource provides the parameters for the Trimming Process.
The process coordinate system is defined as follows: The Y-axis is aligned with the binding edge. It increases from the registered edge to the edge opposite to the registered edge. The X-axis is aligned with the registered edge. It increases from the binding edge to the edge opposite to the binding edge, (i.e., the product front edge).
|
7.2.195 UsageCounter
Many Devices use counters, called “usage counters,” to track equipment utilization or work performed, such as impressions produced or variable data documents generated. Since such usage counters are often used for software and/or hard-ware billing, a mechanism is needed to allow such usage counters to be tracked by MIS for Device utilization statistics and/or costing. The UsageCounter Resource represents a type of equipment or software usage that is tracked by the value of a usage counter used by a Device to count work performed. The Attributes of this Resource indicate what the usage counter is counting. The UsageCounter Elements are modeled as Consumable Resource s, so that standard counting can be used. See Section 3.10.4, “Resource Amount” . The section has details on tracking Amount and ActualAmount , Default units are “countable objects”. See Section 1.6, “Units” .
|
This Attribute indicates the types of usage being counted by the UsageCounter . Insert - post fuser inserter (Media Sides category) OneSided - includes one sided counts (Media Sides category) TwoSided - includes two sided counts (Media Sides category) NormalSize - includes normal size counts (Media Size category) LargeSize - includes large size counts (Media Size category) Black - includes black colorant only counts (Colorant category) Color - includes one or more non-black, non-highlight color colorants counts (Colorant category) Blank - includes entirely blank counts (Colorant category) HighlightColor - includes highlight colorant counts (Colorant category) User - includes counts reflecting work requested by the user, e.g., counts produced by processing the document supplied by the user, as opposed to Auxiliary and Waste. (Usage category) Auxiliary - includes all counts for work not requested by the user, e.g. banner, confirmation, slip, separator, error log. (Usage category) |
||
|
The scope of this usage counter. Lifetime - count since machine last had a firmware reset. must not be specified when UsageCounter is used as a Resource in a JDF ticket. PowerOn - count since the machine was powered on. must not be specified when UsageCounter is used as a Resource in a JDF ticket. |
7.2.196 VarnishingParams
This Resource provides the parameters of a Varnishing Process.
|
See ConventionalPrintingParams . In a Combined Process, all modules of the Device, including press modules are counted to calculate ModuleIndex . |
||
|
The type of module used to apply the Varnish. Only one of ModuleIndex or ModuleType MAY be specified. PrintModule - The Varnish is applied in a printing unit CoatingModule - The Varnish is applied in a specialized coating unit Values include those from: Section C.2, “ModuleType Supported Strings” . |
||
|
Area to be varnished. VarnishArea specifies the requirements for ExposedMedia . |
||
|
Method used for varnishing. VarnishMethod specifies the requirements for ExposedMedia . Blanket - The Varnishing is performed in a CoatingModule. An ExposedMedia with ExposedMedia / Media /@ MediaType = "Blanket" SHOULD be specified. Plate - The Varnishing is performed in a PrintModule or a CoatingModule. An ExposedMedia with ExposedMedia / Media /@ MediaType = "Plate" SHOULD be specified. Independent - No additional ExposedMedia is required. This method MAY be used to specify varnishing in a digital press. |
7.2.197 VerificationParams
This Resource provides the parameters of a Verification Process.
|
Zero-based range list of integers that determines which characters of the data in IdentificationField are to be applied to the field formatting strings. If not specified all characters are applied. |
||
|
Database insertion statement in C printf format defining how information read from the Resource of the Verification Process is to be stored in case of verification errors. The database is defined by the DBSelection Resource of the Verification Process. This field must be specified if a database is selected. |
||
|
Database insertion statement in C printf format defining how information extracted from the IdentificationField is to be stored in case of verification success. The database is defined by the DBSelection Resource of the verification Node. This field must be specified if a database is selected. |
||
|
Ratio of tolerated verification failures to the total number of tests. |
Usage of FieldRange and Format Strings.
A database field name can be calculated from the characters of the IdentificationField using standard C printf notation and the FieldRange Attribute. Each range that is defined in FieldRange is passed to printf as one string that is applied to the format. The order is maintained. Note that SQL was chosen for illustrative purposes only. The mechanism is defined for any database interface.
|
IdentificationField string: |
|
|
Insert "true" into Va where Name = "John Doe" and ID = "1234" |
7.2.198 WebInlineFinishingParams
WebInlineFinishingParams specifies the parameters for Web inline finishing equipment using the WebInlineFinishing Process.
ProductionRun , SubRun , WebName , RibbonName , WebProduct
7.2.199 WireCombBindingParams
This Resource describes the details of the WireCombBinding Process.
|
The name of the comb manufacturer (e.g., Wire-O ®) and the name of the specific item. |
||
|
A more specific, specialized or site-defined name for the color. If ColorDetails is supplied, Color SHOULD also be supplied. |
||
|
The comb diameter is determined by the height of the block of Sheets to be bound. |
||
|
The distance between the “teeth” and the distance between the holes of the prepunched Sheets must be the same. In JDF 1.2 and beyond, use the value implied by HoleMakingParams /@ HoleType . |
||
|
The spine is typically hidden between the last page of the Component and the back cover. Flip the back cover after the wire was “closed” or keep it open. The latter makes sense if further processing is needed (e.g., inserting a CD) before closing the book. |
||
|
The shape of the wire comb binding. Single - Each “tooth” is made with one wire. Twin - The shape of each “tooth” is made with a double wire. |
||
|
Details of the holes in WireCombBinding . |
7.2.200 WrappingParams
WrappingParams defines the details of Wrapping . Details of the material used for Wrapping can be found in the Media Resource that is also an input of the Wrapping Process.
7.3 Device Capability Definitions
The Elements in this section are used to specify capabilities of JDF Devices and provide infrastructure for defining preflight rules, including conducting a “JDF test run” and establishing a handshake between JDF-enabled products. When describing capabilities, note that only Attributes and Elements that are explicitly described within the capabilities structure are supported by the Device. For more details on using capabilities, see Section 7.2.76, “FileSpec” . For more details on preflight, see Section 6.4.26, “Preflight” .
Capabilities descriptions that are saved in files must be formatted as a JMF / Signal / Response to the KnownDevices Query Message.
7.3.1 DeviceCap
The DeviceCap Element describes the JDF Nodes and Resources that a Device is capable of processing. Elements that are derived from the Abstract State Elements are used to describe ranges and lists of ranges of allowed parameters.
|
|
Specifies how the Processes specified in Types are to be specified. If multiple values are specified, the structure of the JDF MUST match one of the values. Combined - The list of Processes in Types must be specified as a Combined Process. CombinedProcessGroup - The list of Processes in Types must be specified either as a Combined Process or as a ProcessGroup of individual Processes. In JDF 1.3 and beyond, the pair of individual tokens: "Combined ProcessGroup" replace this single value. Deprecated in JDF 1.3 GrayBox - The list of Processes in Types must be specified in a ProcessGroup with no nested JDF Nodes, i.e., a Gray Box. New in JDF 1.3 ProcessGroup - The list of Processes in Types must be specified as a ProcessGroup of individual Processes. None - No support for Combined, GrayBox or ProcessGroup . Only one individual Process type defined in Types is supported. |
||
|
Describes the policy for finding and executing JDF Nodes as described in Section 4.2.1, “Determining Executable Nodes” . RootNode - The Device will execute the root JDF Node only. It will not search the JDF tree for executable Nodes. This will commonly be used for sub JDF Nodes that have been spawned and targeted explicitly for the Device. FirstFound - The Device will execute the first Node found in the JDF tree that is executable by this Device. The search order is defined by the order in the XML. AllFound - The Device will execute all executable Nodes found in multiple passes of the JDF tree that are executable by this Device. The results of executing a Node are applied to the tree between passes. |
||
|
List of all generic Attributes that are supported and unrestricted by the Device implementation. Descriptions of Attributes that appear in State Elements (see the following Section 7.3.7, “State”) overwrite the description in GenericAttributes . |
||
|
Specifies the localization(s) provided with the capabilities. If not specified, no localizations are provided. |
||
|
List of optional JDF Node types. The entries of the list must be a subset of Types. Values include those from: JDF /@ Types Example: a RIP with optional in-RIP trapping would specify OptionalCombinedTypes = "Trapping" if Types = "Trapping Interpreting Rendering" . Deprecation note: starting with JDF 1.2, use TypeExpression . |
||
|
JDF Type Attribute of the supported Process. Extension types may be specified by stating the namespace prefix in the value. Values include those from: JDF /@ Type Deprecation note: starting with JDF 1.2, a single value of type is also defined in the Types Attribute. |
||
|
Regular expression that defines the allowed values of the Node's Types Attribute. If not specified, defaults to the literal string defined in Types , (i.e., the ordered list of Processes defined in Types must match exactly). Constraint: in JDF 1.2 and above, one of Types or TypeExpression must be specified. |
||
|
Ordering restriction for Combined Process Nodes and Process Group Nodes. Fixed - The order of Process types specified in the Types Attribute is ordered, and each type can be specified only once, (e.g., Cutting , Folding ). Order does matter. Unordered - The order of Process types specified in the Types Attribute is unordered, and each type can be specified only once, (e.g., DigitalPrinting , Screening , Trapping ). Order does not matter. Unrestricted - The order of Process types specified in the Types Attribute is unordered, and each type can be specified in multiples, (e.g., Cutting , Folding ). The Device can do both Processes, in any order multiple times. Deprecation note: starting with JDF 1.2, use TypeExpression . |
||
|
This Attribute represents the list of supported JDF Node Type values. If any of the Node types are in a namespace other than JDF, the namespace prefix must be included in this Node type name. The ordering is significant unless it is overridden by @ TypeExpression . Constraint: in JDF 1.2 and above, one of Types or TypeExpression must be specified. Values include those from: JDF /@ Types |
||
|
Container for zero of more Action Elements for use as constraints. |
||
|
Pool of DevCap Elements that can be referenced from multiple Elements within the DeviceCap structure. |
||
|
DevCaps * |
List of definitions of the accepted Resources and Elements. The DevCaps Elements are combined with a logical AND, (i.e., a JDF must fulfill all restrictions defined by the set of DevCaps ). Only Resources that are specified within this list are honored by the Device. |
|
|
List of DisplayGroup Subelements, which define the user interface presentation of sets of related DevCap Attribute Values. This is metadata to provide assistance in user interface display layout. |
||
|
List of definitions of the accepted parameter space for Resources and Messages that are for user interface definition only -- they do not map to actual JDF Resources or Messages. Definitions in FeaturePool typically reference macros that manipulate a set of related Resource values. These macros will set the appropriate JDF Attribute Values. |
||
|
Container for zero or more macro Elements, each of which contains an expression that can cause State Attribute Values (e.g., CurrentValue or UserDisplay ) to be changed. |
||
|
Pool of ModuleCap Elements that specify the availability of a given Module. |
||
|
TestPool ? |
Container for zero or more Test Elements that are referenced from ActionPool / Action Elements. |
|
|
State * |
Abstract State Elements that define the parameter space that is covered by the Device. One State Element must be defined for each supported Attribute of the JDF Node that is not specified GenericAttributes or implied by TypeExpression or Types . |
7.3.2 ActionPool
The ActionPool Subelement is used to contain Boolean expressions that are used for two purposes:
- As capability constraints to describe unsupported combinations of State Process and Attribute Values.
- As preflight constraints to describe unsupported combinations of basic PreflightReport values. (See Structure of the Abstract Evaluation Subelement in Section 7.3.13, “Term” . Note that the definition of the Term Element also describes how Boolean operators are employed by Action Elements via the TestRef Attribute.)
ActionPool and the Action Elements it can contain, is interdependent on TestPool and the Test and Term Elements it can contain. For more information on TestPool , see Section 7.3.12, “TestPool” .
|
Action * |
A list of independent Action Elements. |
7.3.2.1 Element: Action
The Action Subelement is used to contain Boolean expressions that are used to describe a constraint that describes an unsupported combination of State Process and Attribute Values. If the Test referenced by TestRef evaluates to "true" , the combination of Processes and Attribute Values described is not allowed, and the action indicated by "Error" , "Warning" or "Information" in the Severity Attribute must be taken.
|
Indicates how the severity of the failure is to be treated when the expression defined by TestRef is violated. Error - The client is to display an error message and not allow the conflicting settings to persist. Warning - The client is to notify the user of the condition but allow the settings to persist if the user requests. Information - The client is to allow the settings to persist but inform the user of the issue. |
||
|
Unique identifier of the Action Element. This ID is used to refer to the Action Element, (e.g., from a preflight report). |
||
|
Reference to a Test Element that is executed to evaluate this Action . |
||
|
Loc * |
Text to describe an error if the Test fails. (See Section 7.3.5.1, “Loc” .) |
|
|
Provides additional constraints that are specific to the Preflight Process. See Section 7.2.139, “PreflightParams” . |
7.3.3 DevCapPool
The DevCapPool provides a container for descriptions of Elements that are referenced from multiple locations within the JDF.
|
DevCap + |
DevCap Elements that can be referenced from multiple locations within the DeviceCap structure. DevCap / @ID must be specified for all DevCap Elements in DevCapPool . |
7.3.4 ModulePool
|
ModuleCap Elements that can be referenced from within the DeviceCap structure to specify features that depend on a given module being installed. |
7.3.4.1 ModuleCap
Module elements specify features that depend on given hardware or software modules being installed. Hardware examples include duplex units for printers. Software licensing keys may also be modeled as modules.
|
Specifies whether the feature described by this State Element is available on the Device. Installed - The feature is installed on the Device and is available for use. Module - Module is not to be specified recursively in a ModuleCap . This value is only specified here to have a common enumeration set for all Availability Attributes. NotInstalled - The feature has not been installed on the Device. NotLicensed - The feature has been installed on the Device but can not be used until licensed. Disabled - The feature is installed and licensed on the Device, but has been disabled. |
||
|
ID of the ModuleCap . |
||
|
ID of the module that this ModuleCap describes. Refers to Device / Module /@ ModuleID . If neither ModuleID nor ModuleIndex are specified, no further details of the Module are known. |
||
|
Index of the module that this ModuleCap describes. Refers to Device / Module /@ ModuleIndex . If neither ModuleID nor ModuleIndex are specified, no further details of the Module are known. |
7.3.5 DevCaps
The DevCaps Element describes the valid parameter space of a JDF Resource, Message or ResourceLink that is consumed, honored or produced by a Device. Note that DevCaps not only describes the structure of the individual Resource and ResourceLink Elements but also of the AuditPool or other direct child Elements within a JDF Node. The DevCaps Element may be used to model Intent Resource s as well as Process definition Resources.
|
Specifies whether the feature described by this DevCaps Element is available on the Device. Installed - The feature is installed on the Device and is available for use. Module - The feature is provided by a module specified in ModuleRefs . If and only if all modules that are listed in ModuleRefs are available, the feature is available. New in JDF 1.3 NotInstalled - The feature has not been installed on the Device. NotLicensed - The feature has been installed on the Device but can not be used until licensed. Disabled - The feature is installed and licensed on the Device but has been disabled. |
||
|
Describes whether the DevCaps context is within a Resource or a link to a Resource (not applicable to DevCaps Elements within Messages). Element - The DevCaps context is describing a direct Element, e.g., an AuditPool . JMF - The DevCaps context describes a JMF Message. Link - The DevCaps context is describing a link to a Resource. Resource - The DevCaps context is describing a Resource. |
||
|
Reference to reusable DevCap Elements that are located in DeviceCap / DevCapPool . A reference to a DeviceCap / DevCapPool / DevCap is equivalent to an inline DevCap in this DevCaps . Exactly one of DevCapRef or DevCap must be specified. |
||
|
ID of this DevCaps Element. Used for reference from Performance Elements. |
||
|
Used when the Context of this DevCaps = "Resource" or "Link" . This field qualifies whether the DevCaps describes a Resource used as an input to a Process or as the output of a Process. Default behavior: this DevCaps applies to both usages. Input - The DevCaps describes an Input Resource. Output - The DevCaps describes an Output Resource. |
||
|
List of modules that are needed for this feature to be available. At least one entry must be specified if Availability = "Module" . The list of Modules is specified in DeviceCap / ModulePool . |
||
|
Name of the Element excluding the namespace prefix. When describing parameters of a ResourceLink , Name must be the name of the referenced Resource and Context = "Link" . When DevCaps is specified as a Subelement of MessageService , Name specifies the respective CommandTypeObj , QueryTypeObj or ResponseTypeObj of the JMF Message. Modification note: starting with JDF 1.3, Name must always specify the actual Resource name. Before JDF 1.3, the ResourceUsage and ProcessUsage of a Resource are specified in this Attribute. Values include those from: Chapter 7, “Resources”. |
||
|
ResourceLink /@ ProcessUsage of the link to the Resource that is described by this DevCaps . Values include those from: ResourceLink /@ ProcessUsage |
||
|
If "true" , the Element described by this DevCaps Element must be present in a JDF or JMF (as appropriate) submitted to the Device. Note that this does not override the cardinality defined by the JDF specification when the specification requires the Resource to be specified. If an Attribute is required (according to this specification), Required must be "true" . |
||
|
Specifies the capability to handle partial updates defined in ResourceUpdate Elements. None - ResourceUpdate is not supported. must not be combined with any other value. JMFID - JMF Resource Messages that reference ResourceUpdate Elements that have been previously loaded to the Device are accepted. PDLID - References from PDL data, (e.g., PPML TicketRef elements that reference ResourceUpdate Elements that have been previously loaded to the Device are accepted). |
||
|
Resource /@ ResourceUsage of the Resource that is described by this DevCaps . Values include those from: FileSpec /@ ResourceUsage |
||
|
Specifies which occurrence(s) of the JDF Node type that is specified either within the DeviceCap /@ Types or by DeviceCap /@ TypeExpression that the Element that is defined by this DevCaps applies to. If not specified, this DevCaps Element describes Elements belonging to all JDF Nodes or Combined Process steps with a matching type that are not defined by other DevCaps entries. Note: this is an index into the list of matching Type values and not an index into the complete list specified by Types or TypeExpression . The first occurrence is "0" , and the last occurrence is "-1" , etc. |
||
|
List of JDF Node types that a DevCaps applies to. The value of Types must be a subset of Types in DeviceCap . Values include those from: JDF /@ Types Deprecation note: starting with JDF 1.2, use TypeOccurrenceNum . |
||
|
DevCap * |
List of definitions of the accepted parameter space for Resources and Messages. The parameter spaces of multiple DevCap Elements are combined as a superset of the individual DevCap Elements. Only Elements that are explicitly specified as DevCap Elements within a DevCaps are supported. When a capabilities description is constructed using constraints, each DevCaps should contain only a single DevCap Element (although a DevCap Element may still contain multiple DevCap Subelements). Exactly one of DevCapRef or DevCap must be specified, though if DevCap is specified, it may occur multiple times. |
|
|
Loc * |
The localization(s) of the Resource, Message or ResourceLink name as described by this DevCaps Element. (See Section 7.3.5.1, “Loc” .) |
7.3.5.1 Loc
Each Loc element describes a localization for some value. Note that this Subelement is used in many of the Elements subordinate to DeviceCap Elements.
|
Localized text used for supplemental help for the value being localized. Note that this is the text often used for a pop-up window when help is requested. |
||
|
The language code for this localization. If not specified, then it defaults to the value of the first language specified in the Lang Attribute of the DeviceCap Element. Note that each language in a list of localizations (i.e., Loc *) must be unique. |
||
|
The short form of the localization. Defaults to the value of Value . This value would be used when a small fixed field is required for the name of the field (a PDA for example). |
||
|
The localization of the value being localized. If not specified, then the value being localized is used as the Value , (e.g., the Resource , ResourceLink , Element, Message, Attribute name or Attribute Value). |
7.3.6 DevCap
The DevCap Element describes the valid parameter space of a JDF Resource, Message or Element that is consumed or produced by a Device. The structure of the DevCap is identical to that of the JDF Resource, Message or Element that it models. Individual Attributes are replaced by the appropriate State Elements. For more details on State Elements, see Section 7.3.7, “State”. The Name Attribute of the State Element must match the Attribute key that is described. If no State Element exists for a given Attribute, it is assumed to be unsupported. The restrictions of multiple Attributes and Elements are combined with a logical AND.
Subelements of Resources are modeled by including nested DevCap with a ResourceUsage Attribute equal to the Subelements tag name or ResourceUsage if the Subelement is a FileSpec . Attributes of the ResourceLink belonging to the Resource , (e.g., Transformation or the various pipe control parameters can also be restricted).
|
Specifies whether the feature described by this DevCap Element is available on the Device. Default value is from: parent DevCaps /@ Availability or DevCap /@ Availability . Installed - The feature is installed on the Device and is available for use. Module - The feature is provided by a module specified in ModuleRefs . If and only if all modules that are listed in ModuleRefs are available, the feature is available. New in JDF 1.3 NotInstalled - The feature has not been installed on the Device. NotLicensed - The feature has been installed on the Device but can not be used until licensed. Disabled - The feature is installed and licensed on the Device but has been disabled. |
||
|
References to reusable DevCap Elements that are located in DeviceCap / DevCapPool . A reference to a DeviceCap / DevCapPool / DevCap is equivalent to an inline DevCap in this DevCap . If both DevCapRefs and DevCap Elements exist, they specify the union of both. |
||
|
Namespace of the Element that is described by this DevCap . |
||
|
ID of this DevCap . Used to reference a DevCap . DevCap /@ ID must be specified for all direct DevCap child Elements in DevCapPool . |
||
|
Maximum number of occurrences of the Element described by this DevCap . |
||
|
Minimum number of occurrences of the Element described by this DevCap . |
||
|
List of modules that are needed for this feature to be available. At least one entry must be specified if Availability = "Module" . The list of Modules is specified in DeviceCap / ModulePool . |
||
|
Name of the Resource that is described. Default, if this DevCap is the direct child of a DevCaps Element: the value of the parent DevCaps / @Name . Name must be specified for all direct DevCap child Elements in DevCapPool or DevCap Elements. Modification note: starting with JDF 1.3, Name must always specify the actual Resource name. Before JDF 1.3 ResourceUsage of a Resource was specified in this Attribute. Values include those from: Chapter 7, “Resources”. |
||
|
Resource /@ ResourceUsage of the Resource that is described by this DevCap . Values include those from: FileSpec /@ ResourceUsage |
||
|
DevCap * |
Definition of the accepted parameter space for the Messages or Resources Subelements. If Multiple DevCap Elements with the same @Name exist, they describe individual Subelements with different properties. The properties must each be fulfilled by individual Subelements of the Element that is described by this DevCap . For instance, if two DevCap Elements with the MinOccurs = "1" are specified, the JDF Element must contain two Elements with a Node name = DevCap /@ Name . |
|
|
Loc * |
The localization(s) of the Element name. (See Section 7.3.5.1, “Loc” .) |
|
|
State * |
Abstract State Elements that define the parameter space that is covered by Device. One State Element must be defined for each supported Attribute or Intent Span Element of the Element that this DevCap defines that is not specified DeviceCap /@ GenericAttributes . |
7.3.7 State
Figure 7-76 shows all State Elements.
|
7.3.7.1 Abstract State Element
Table 7-403 describes the common, data type-independent parameters of all State Elements. The State Elements that contain no value restriction Attributes (e.g. AllowedValueList ) or Elements (e.g. ValueLoc ) have no further restrictions other than the data type of their values. If value restrictions are specified in addition to a list of explicit values in AllowedValueList, CurrentValue, Value or ValueLoc , the State Element describes the union of restrictions, i.e., the State Element matches an Attribute that matches either the explicit list or the additional restrictions.
|
Specifies whether the feature described by this State Element is available on the Device. Default behavior: the value specified or implied by the parent Element Installed - The feature is installed on the Device and is available for use. Module - The feature is provided by a module specified in ModuleRefs . If and only if all modules that are listed in ModuleRefs are available, the feature is available. New in JDF 1.3 NotInstalled - The feature has not been installed on the Device. NotLicensed - The feature has been installed on the Device but can not be used until licensed. Disabled - The feature is installed and licensed on the Device, but has been disabled. |
||
|
Zero or more references to Action Elements that operate on the parameter. All Action Elements referenced must evaluate to "false" for the value of the State Element to be valid. Any Action Elements referenced in ActionRefs should be evaluated whenever the Attribute described by this State Element is manipulated or changed in order to catch any Attributes that become invalid due to the manipulation. |
||
|
A reference to a macro that conditionally modifies the UserDisplay Attribute of this State Element. If present, this referenced macro is to be executed when the State /@ UserDisplay is "Dependent" and the user interface is being initialized. It is recommended that the macro referenced by DependentMacroRef only change the value of UserDisplay or Editable Attributes. For more information on macro definitions, see Section 7.3.10, “MacroPool” . |
||
|
Namespace of the Attribute that is described by this State Element. |
||
|
When "true" , the feature and its current value can be edited by the user. If "false" , the user interface must not allow user modification of the State Element’s current value. |
||
|
A flag that describes whether the parameter has a default supplied by the Device. If set, DefaultValue must be set. |
||
|
ListType = "SingleValue" |
Specifies what type of list or object the State variable describes. Values are from: Table 7-404, “ListType Attribute Values”. |
|
|
Zero or more references to macro Elements that operate on the parameter. These macro Elements set other State Attribute Values as appropriate. Any macro Elements referenced in MacroRefs is to be evaluated whenever the Attribute described by this State Element is manipulated or changed to affect any necessary changes to other Attributes. The macro Elements can change Attributes such as the CurrentValue Attribute of a State or its UserDisplay Attribute. For more information on macro definitions, see Section 7.3.10, “MacroPool” . |
||
|
Maximum number of Elements in the list described by this State , (e.g., the maximum number of integers in an integer list). If MaxOccurs is not "1" , the State Element refers to a list or a range of list values, (e.g., a NameState will allow a list of NMTOKENS). |
||
|
Minimum number of Elements in the list described by this State . If MinOccurs is not "1" , the State Element refers to a list or a range of list values, (e.g., a NameState will allow a list of NMTOKENS). |
||
|
List of modules that are needed for this feature to be available. At least one entry must be specified if Availability = "Module" . The list of Modules is specified in DeviceCap / ModulePool . |
||
|
Name of the Attribute that is described by this State . If Name is omitted this State describes the Element’s text, (i.e., the text between the XML start and end tag). |
||
|
If "true" , then the Attribute or Span Element described by this State Element is required to be present in a JDF or JMF (as appropriate) submitted to the Device. Note that this does not override the cardinality specified by the JDF specification where the specification requires the Element to be specified. |
||
|
A flag that describes whether the parameter is an intent span data type. For example a State Element describing an XYPairSpan would have DataType = "XYPairState" and Span = "true" . |
||
|
Indicates whether the feature is to be displayed in user interfaces. Display - The feature is to be displayed. Hide - The feature is not to be displayed. Dependent - The feature is to be conditionally displayed depending on the action specified by the macro referenced by DependentMacroRef . Note: this action is only taken when the user interface is first initialized. |
||
|
Loc * |
The localization(s) of the Name of the Attribute that is described by this State Element. (See Section 7.3.5.1, “Loc” .) |
-- Attribute: ListType
|
The State describes a list of individual values. Each value must occur exactly once. |
|
|
The State describes an ordered list of individual values. Each value must occur exactly once and in the specified order. |
|
|
The State describes a list of individual values. The State = "true" if at least one of the values occurs. This value is only expected to be used in BasicPreflightTest Elements. |
|
|
The State describes a list of individual values. |
|
|
The State describes an ordered list of individual values. |
|
|
The State describes an ordered RangeList of individual values. |
|
|
The State describes an individual Range of values. |
|
|
The State describes an individual value. |
|
|
The State describes a Span Element in an Intent Resource . |
|
|
The State describes a list of individual values. Each value MUST NOT occur more than once. |
|
|
The State describes a RangeList of values. Each explicit or implied value MUST NOT occur more than once. |
|
|
The State describes an ordered list of individual values. Each value MUST NOT occur more than once. |
|
|
The State describes an ordered RangeList of individual values. Each explicit or implied value MUST NOT occur more than once. |
7.3.7.2 State Elements
The following types of State Elements are defined:
|
Describes a range of matrices. Generally used to define valid orientations of Component Resources. |
||
7.3.7.2.1 BooleanState
This State Subelement is used to describe ranges of Boolean values. It inherits from the Abstract State Element described above.
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
A list of all supported values that can be chosen without operator intervention. |
||
|
ValueLoc * |
Localization(s) of "true" and/or "false" values. See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.7.2.1.1 ValueLoc
Each ValueLoc Element describes one or more localizations for an Attribute Value. Note that the ValueLoc Element occurs in the definition of all State Elements except MatrixState , PDFPathState and StringState .
|
The Attribute Value to be localized. If the data type of the allowed value is not string (e.g., if ValueLoc is used in the context of a MatrixState ), Value must be an instance of the appropriate data type. |
||
|
Loc * |
The localization(s) of the Attribute Value. See Section 7.3.5.1, “Loc” . |
7.3.7.2.2 DateTimeState
This State Subelement is used to describe ranges of dateTime values. It inherits from the Abstract State Element described above.
|
List of inclusive minimum and maximum allowed values relative to the current system time. |
||
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
List of inclusive minimum and maximum allowed values that can be chosen without operator intervention relative to the current system time. If not specified, the value of AllowedValueDurationList is applied. |
||
|
Inclusive minimum and maximum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueList is applied. |
||
|
ValueLoc * |
Localization(s) of specific dates. See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.7.2.3 DurationState
This State Subelement is used to describe ranges of duration values. It inherits from the Abstract State Element described above.
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
Inclusive minimum and maximum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueList is applied. |
||
|
ValueLoc * |
Localization(s) of specific durations. See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.7.2.4 EnumerationState
This State Subelement is used to describe ranges of enumerative values. It inherits from the Abstract State Element described above. It is identical to the NameState Element except that it describes a closed list of enumeration values.
|
A list of all supported values. The values specified in AllowedValueList must be a subset of the enumeration specified by Name . If not specified, all enumerations defined by the XML schema are valid. In order to enable capabilities to be specified without access to the JDF XML schema, it is strongly recommended to specify AllowedValueList , even when the entire range of schema-valid values is supported. |
||
|
Current value for the current running Job set in the Device. CurrentValue must match the enumeration defined in the Resource. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must match the enumeration defined in the Resource, and must be specified if HasDefault = "true" . |
||
|
A list of values that can be chosen without operator intervention. PresentValueList must match the enumeration defined in the Resource. |
||
|
ValueLoc * |
Localizations of the enumerations listed in AllowedValueList and PresentValueList . See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.7.2.5 IntegerState
This State Subelement is used to describe ranges of integer values. It inherits from the Abstract State Element described above.
|
Inclusive maximum allowed value. Replaced by AllowedValueList in JDF 1.2 and beyond. |
||
|
Inclusive minimum allowed value. Replaced by AllowedValueList in JDF 1.2 and beyond. |
||
|
X defines the Modulo and Y the offset of the allowed value. In other words, if AllowedValueMod = "10 2" , only the values ... -8,2,12,22 ... are allowed. If not specified, all values in the range are valid. If ((N%X)-Y = 0) then N is a valid value. Note: “Modulo” is the remainder of an integer division. For example: 4 mod 3 = 4 -3 = 1; 17 mod 3 = 17-5*3 = 2; and 3 mod 3 = 3-3 = 0. |
||
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
A list of values that can be chosen without operator intervention. If not specified, the value of AllowedValueList is applied. |
||
|
Inclusive maximum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueMax is applied. Replaced by PresentValueList in JDF 1.2 and beyond. |
||
|
Inclusive minimum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueMin is applied. Replaced by PresentValueList in JDF 1.2 and beyond. |
||
|
X defines the Modulo and Y the offset of the present value. In other words, if AllowedValueMod = "10 2" , only the values ... -8,2,12,22 ... are allowed. If not specified, the value of AllowedValueMod is applied. If ((N%X)-Y = 0) then N is a valid value. |
||
|
Specifies the unit type that this State Element represents. Used to enable an application to localize the representation of the units. UnitType should be specified if the IntegerState represents a value that has units. User interfaces might not display correctly if UnitType is not specified for Attributes with units. Angle - The Attribute is defined in degrees. AngularVelocity - Rotations / minute. Area - Area in square meters (m2). Currency - The local currency. Length - In points (1/72 inch). LengthMu - Length in microns (used for paper thickness). LineScreen - The lines per inch (lpi) for conventionally screened halftone, screened grayscale and screened monotone bitmap images. PaperWeight - In grams per square meter ( g /m2). Percentage - A percentage value. Resolution - The dots per inch (dpi) for print output and bitmap image (e.g., TIFF or BMP) file resolution. ScreenResolution - The pixels per inch (ppi) for screen display (e.g., softproof display and user interface display), scanner capture settings and digital camera settings. SpotResolution - For imaging Devices such as filmsetters, platesetters and proofers, the fundamental imaging unit, (e.g., one “on” laser or imaging-head imaged unit). Note that many imaging Devices construct dots from multiple imaging spots, so dpi and spots per inch (spi) are not equivalent. Temperature - Temperature in degrees Centigrade. |
||
|
ValueLoc * |
Localization(s) of specific values. See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.7.2.6 MatrixState
This State Subelement is used to describe ranges of matrix values. It inherits from the Abstract State Element described above. It is primarily intended to specify orientations and manipulation capabilities of Physical Resource s, (e.g., in finishing Devices).
|
Allowed Modulo of the allowed rotations and offset in degrees. |
||
|
Minimum and maximum allowed shift of the matrix. If not specified, any shift is valid. If AllowedTransforms is specified, the implied shift defined in Table 2-4, “Matrices and Orientation values for describing the orientation of a Component” is subtracted from AllowedShift , thus all in-place rotations have an implied AllowedShift value of "0 0 0 0" . (No shift = "0 0 0 0" .) The first pair of numbers is the XY pair that defines the minimum shift, and the second pair is the XY pair that defines the maximum shift. |
||
|
List of valid orthogonal transformations of the matrix. Any of the eight predefined transforms for Physical Resource s as defined in Table 2-4, “Matrices and Orientation values for describing the orientation of a Component”. |
||
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
Present Modulo of the allowed rotations and offset in degrees that can be chosen without operator intervention. |
||
|
If PresentTransforms is specified, the implied shift defined in Table 2-4, “Matrices and Orientation values for describing the orientation of a Component” is subtracted from PresentShift , thus all in-place rotations have an implied PresentShift value of "0 0 0 0" . If not specified, the value of AllowedShift is applied. |
||
|
Any of the eight predefined transforms for Physical Resource s as defined in Table 2-4, “Matrices and Orientation values for describing the orientation of a Component”. If not specified, the value of AllowedTransforms is applied. |
||
|
Value * |
A list legal values. See Section 7.3.7.2.6.1, “Value”. |
7.3.7.2.6.1 Value
|
A legal value for a matrix variable that can be chosen without operator intervention. If not specified, the value of AllowedValue is applied. In JDF 1.2 and beyond, use ValueUsage . |
||
|
Defines whether the value defined in AllowedValue means Present , Allowed or both. Default behavior: valid for both Present and Allowed . |
||
|
Loc * |
The localization(s) of the string defined in AllowedValue. See Section 7.3.5.1, “Loc” . |
7.3.7.2.7 NameState
This State Subelement is used to describe ranges of NMTOKEN values. It inherits from the Abstract State Element described above.
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
Regular expression that limits the values that can be chosen without operator intervention. If not specified, the value of AllowedRegExp is applied. |
||
|
A list of values that can be chosen without operator intervention. If not specified, the value of AllowedValueList is applied. |
||
|
ValueLoc * |
Localization(s) of the NMTOKENS listed in AllowedValueList or PresentValueList or implied by AllowedRegExp or PresentRegExp . See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.7.2.8 NumberState
This State Subelement is used to describe ranges of double values. It inherits from the Abstract State Element described above.
|
Inclusive maximum allowed value. Replaced by AllowedValueList in JDF 1.2 and beyond. |
||
|
Inclusive minimum allowed value. Replaced by AllowedValueList in JDF 1.2 and beyond. |
||
|
X defines the Modulo and Y the offset of the allowed value. In other words, if AllowedValueMod = "10 2" , only the values ... -8,2,12,22 ... are allowed. If not specified, all values in the range are valid. If ((N%X)-Y = 0) then N is a valid value. Note: “Modulo” is the remainder of an integer division. For example: 4 mod 3 = 4 -3 = 1; 17 mod 3 = 17-5*3 = 2; and 3 mod 3 = 3-3 = 0. |
||
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
A list of values that can be chosen without operator intervention. If not specified, the value of AllowedValueList is applied. |
||
|
Inclusive maximum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueMax is applied. Replaced by PresentValueList in JDF 1.2 and beyond. |
||
|
Inclusive minimum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueMin is applied. Replaced by PresentValueList in JDF 1.2 and beyond. |
||
|
X defines the Modulo and Y the offset of the allowed value. In other words, if AllowedValueMod = "10 2" , only the values ... -8,2,12,22 ... are allowed. If not specified, the value of AllowedValueMod is applied. |
||
|
Specifies the unit type that this State Element represents. Used to enable an application to localize the representation of the units. UnitType must be specified if the NumberState represents a value that has units. NumberState has the values as IntegerState plus a few more: CMYKColor - Four values representing a CMYK color. LabColor - Three values representing a Lab color. sRGBColor - Three values representing a sRGB color. Values include those from: IntegerState /@ UnitType ( Table 7-411, “IntegerState Element” ). |
||
|
ValueLoc * |
Localization(s) of specific values. See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.7.2.9 PDFPathState
This State Subelement is used to describe ranges of PDF paths. It inherits from the Abstract State Element described above.
|
Inclusive minimum and maximum length of valid PDF path in multi-byte characters. Note that this is the length in characters and not in bytes of the internal encoding of an application. |
||
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
Inclusive minimum and maximum length of valid PDF path in characters that can be chosen without operator intervention. If not specified, the value of AllowedLength is applied. |
||
|
Value * |
The localization(s) of the PDF path defined in AllowedValue . See Section 7.3.7.2.9.1, “Value”. |
7.3.7.2.9.1 Value
|
Defines whether the value defined in AllowedValue means Present , Allowed or both. Default behavior: valid for both Present and Allowed . |
||
|
Loc * |
The localization(s) of the string defined in AllowedValue. See Section 7.3.5.1, “Loc” . |
7.3.7.2.10 RectangleState
This State Subelement is used to describe ranges of rectangle values. It inherits from the Abstract State Element described above.
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
Allowed relative value of width (X) vs. Height (Y). If not specified, the value of AllowedHWRelation is applied. |
||
|
A list of ranges of values that can be chosen without operator intervention. If not specified, the value of AllowedValueList is applied. |
||
|
ValueLoc * |
A list of supported values. The ValueLoc /@ Value Attribute must be a representation of a rectangle. This can also be used to localize (or provide names for) specific rectangles. See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.7.2.11 ShapeState
This State Subelement is used to describe ranges of Shape values. It inherits from the Abstract State Element described above.
|
Inclusive maximum allowed value. Replaced by AllowedValueList in JDF 1.2 and beyond. |
||
|
Inclusive minimum allowed value. Replaced by AllowedValueList in JDF 1.2 and beyond. |
||
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true". |
||
|
A list of values that can be chosen without operator intervention. If not specified, the value of AllowedValueList is applied. |
||
|
Inclusive maximum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueMax is applied. Replaced by AllowedValueList in JDF 1.2 and beyond. |
||
|
Inclusive minimum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueMin is applied. Replaced by AllowedValueList in JDF 1.2 and beyond. |
||
|
Present X-axis of the Shape that can be chosen without operator intervention. If not specified, the value of AllowedX is applied. |
||
|
Present Y-axis of the Shape that can be chosen without operator intervention. If not specified, the value of AllowedY is applied. |
||
|
Present Z-axis of the Shape that can be chosen without operator intervention. If not specified, the value of AllowedZ is applied. |
||
|
ValueLoc * |
A list of supported shapes. See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.7.2.12 StringState
This State Subelement is used to describe ranges of string values. It inherits from the Abstract State Element described above.
|
Inclusive minimum and maximum length of valid string in multi-byte characters. Note that this is the length in characters, and not in bytes of the internal encoding of an application. For instance, the length of the string "Grün" is 4 and not 6 (UTF-8 with a terminating 0 and a double byte "ü" ). |
||
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
Inclusive minimum and maximum length of valid string in characters that can be chosen without operator intervention. If not specified, the value of AllowedLength is applied. |
||
|
Regular expression that limits the present values that can be chosen without operator intervention. If not specified, the value of AllowedRegExp is applied. |
||
|
Value * |
A list legal values. See Section 7.3.7.2.12.1, “Value”. |
7.3.7.2.12.1 Value
|
A legal value for a string variable that can be chosen without operator intervention. If not specified, the value of AllowedValue is applied. In JDF 1.2 and beyond, use ValueUsage . |
||
|
Defines whether the value defined in AllowedValue means Present , Allowed or both. Default behavior: valid for both Present and Allowed . |
||
|
Loc * |
The localization(s) of the string defined in AllowedValue . See Section 7.3.5.1, “Loc” . |
7.3.7.2.13 XYPairState
This State Subelement is used to describe ranges of XYPair values. It inherits from the Abstract State Element described above.
|
Inclusive maximum allowed value. Replaced with AllowedValueList in JDF 1.2 and beyond. |
||
|
Inclusive minimum allowed value. Replaced with AllowedValueList in JDF 1.2 and beyond. |
||
|
Current value for the current running Job set in the Device. |
||
|
Default value if not specified in a submitted JDF. DefaultValue must be specified if HasDefault = "true" . |
||
|
A list of values that can be chosen without operator intervention. If not specified, the value of AllowedValueList is applied. |
||
|
Inclusive maximum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueMax is applied. Replaced with PresentValueList in JDF 1.2 and beyond. |
||
|
Inclusive minimum allowed value that can be chosen without operator intervention. If not specified, the value of AllowedValueMin is applied. Replaced with PresentValueList in JDF 1.2 and beyond. |
||
|
Relative value of X vs. Y that can be chosen without operator intervention. If not specified, the value of AllowedXYRelation is applied. |
||
|
Specifies the unit type that this State Element represents. Used to enable an application to localize the representation of the units. UnitType must be specified if the IntegerState represents a value that has units. Values include those from: IntegerState /@ UnitType ( Table 7-411, “IntegerState Element” ). |
||
|
ValueLoc * |
A list of supported shapes. See Section 7.3.7.2.1.1, “ValueLoc” . |
7.3.8 DisplayGroupPool
The DisplayGroupPool Element declares set(s) of related features that are intended to be displayed as a group in user interfaces. These declarations are references to individual features declared in State Elements.
|
Declares a set of references to State Elements that are intended to be displayed as a group in user interfaces. |
Example 7-57: DisplayGroupPool
In this example, a single DisplayGroup is specified. This DisplayGroup declares that the State Attributes with ID ’s "btd" , "cmp" , "mag" , "colorspace" and "outputres" are all to be grouped together in any user interface. The English string “ ScanningParameters ” is associated with this DisplayGroup , though no explicit assumptions are made about how to display this group of Attributes. The DisplayGroup Element merely states that there is a user-significant relationship between the Attributes.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<Device Class="Implementation" ID="Link0003" Status="Available">
< DisplayGroup rRefs = "bad" >
< Loc HelpText = "Parameters for scanning configuration" Lang = "en"
Value = "ScanningParameters" />
<DeviceLink Usage="Input" rRef="Link0003"/>
7.3.8.1 DisplayGroup
Each DisplayGroup Element declares a group of features that are intended to be displayed together in user interfaces.
|
References to State Elements. (See Section 7.3.7, “State” for details of the State Element.) |
||
|
Loc * |
Localized strings describing the DisplayGroup . See Section 7.3.5.1, “Loc” . |
7.3.9 FeaturePool
The FeaturePool Element describes Message or Resource Subelements that represent composite features for user manipulation when describing capabilities. These features typically do not directly represent any JDF Resources or parameters., but rather trigger macros that manipulate related sets of parameters. For more information on macro definitions, see Section 7.3.10, “MacroPool” .
These features can be mapped to JDF /@ NamedFeatures . A feature from JDF / @NamedFeatures is selected by specifying an NMTOKEN pair that matches entries from FeaturePool / EnumerationState /@ Name and FeaturePool / EnumerationState /@ AllowedValueList
|
State * |
Abstract State Elements that define the accepted parameter space for the Messages or Resources Subelements. These Abstract Subelements are identical in form to other State Elements, but typically are only “macro” features that control other features through macro Elements. For more information on macro definitions, see Section 7.3.10, “MacroPool” . For details of the State Element, see Section 7.3.7, “State” . |
Example 7-58: FeaturePool
In this example, ScanMode is a feature that doesn't map directly to any JDF Resource or Attribute, but provides a “shell” feature that allows users to control a set of JDF Resources and/or Attributes to indicate a common or preferred grouping based on the user’s desired task. The actual corresponding JDF Resource Attribute Values are determined and set by the ScanModeMacro macro that is called when the ScanMode feature is manipulated.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<Device Class="Implementation" ID="Link0003" Status="Available">
AllowedValueList = "Mono ColorTransparency Photo" ID = "sm"
HasDefault = "false" MacroRefs = "ScanModeMac" Name = "ScanMode"
<DeviceLink Usage="Input" rRef="Link0003"/>
7.3.10 MacroPool
The MacroPool Element is used to contain descriptions of macro expressions. Each macro declares a set of conditional operations that are used to change State Element Attribute Values.
|
macro * |
|
7.3.10.1 macro
The macro Subelement is used to contain a set of conditional operations that are used to change State Element Attribute Values. Each macro contains one or more of the following Elements:
- choice -- Declares one or more when statements, each of which contains a Boolean expression (as defined in Section 7.3.13, “Term” ) and a set Element. When the expression evaluates to "true" , the action specified in the set Element is to be performed. If no evaluation in any when Element in a choice evaluates to "true" , the action(s) specified in the otherwise Element is to be performed.
- set -- sets the condition of one or more State Element Attributes.
- call -- calls another macro to be executed.
When executing a macro , consumers must execute choice , set and call Elements in the order in which they are specified in the actual XML document. Note that the ordering provided in the actual capabilities description should be honored. The following shows the logical layout of the macro Subelement:
|
Unique identifier of a macro Element. This ID is used to refer to the macro Element. |
||
|
choice * |
A set of conditional operations that set (or not) feature values. At least one of choice , set or call must be specified in macro . |
|
|
set * |
An Element that sets one or more State Attribute Values. At least one of choice , set or call must be specified in macro . |
|
|
call * |
An Element that calls another macro , allowing for macro reuse and chaining. At least one of choice , set or call must be specified in macro . |
7.3.10.2 choice
The choice Subelement is used to contain expressions that declare conditional operations that can cause State Element Attribute Values to be changed. The choice includes one or more when statements that are evaluated in order, each of which contains a Boolean expression (as defined in Section 7.3.13, “Term” ) and a set Element. When the expression evaluates to "true" , the action specified in the set Element is to be performed and no further when statements are evaluated. If no evaluation in any when Element in a choice evaluates to "true" , the action(s) specified in the otherwise Element is to be performed.
|
when + |
A set of conditional operations that set (or not) feature values. |
|
|
An Element that sets one or more State Element Attribute Values if none of the when expressions evaluate to "true" . |
7.3.10.3 otherwise
The otherwise Subelement sets one or more feature values if none of the when expressions in a choice Element evaluate to "true" .
|
set + |
7.3.10.4 when
The when Subelement is used to contain expressions that declare conditional operations to enforce sets of feature behaviors. The when Element includes a Boolean expression (as defined in Section 7.3.13, “Term” ) and a set Element. When the Term evaluates to "true" , the action specified in the set Element is to be performed.
|
A Boolean expression that evaluates a set of feature values. |
||
|
set + |
7.3.10.5 set
The set Subelement sets one or more State Element Attribute Values.
|
Reference to a State Element referring to the feature value to set |
||
|
Specifies one or more Attributes within the State Element that are to have their value changed (along with the value they change to). |
7.3.10.6 FeatureAttribute
FeatureAttribute specifies one or more Attributes of a State Element that are to have their value changed. The following Attributes can be changed:
|
The value to change the CurrentValue Attribute of the State Element to. Note that the mapping of the string to the actual data type of the State Element must be performed by the application processing the capabilities. |
||
|
When "true" , the feature and its current value can be edited by the user. If "false" , the user interface must not allow user modification of the current value of the State Element. |
||
|
Indicates under which conditions the feature is to be displayed in user interfaces. Values are from: State /@ UserDisplay |
7.3.11 Performance
The Performance Element describes speed as the capability to consume or produce a JDF Resource.
|
Average amount produced/consumed per hour assuming an average Job. |
||
|
Reference to the DevCaps Element that describes the Resource whose performance is specified by this Performance Element. |
||
|
Maximum amount produced/consumed per hour, assuming an ideal Job. The default value of "0" translates to the value of AverageAmount . |
||
|
Maximum time needed to clean the Device after a Job, assuming a worst case Job. Defaults to AverageCleanup . |
||
|
Maximum time needed to setup the Device before a Job, assuming a worst case Job. Defaults to AverageSetup . |
||
|
Minimum amount produced/consumed per hour, assuming a worst case Job. Defaults to AverageAmount . |
||
|
Minimum time needed to clean the Device after a Job, assuming an ideal Job. Defaults to AverageCleanup . |
||
|
Minimum time needed to setup the Device before a Job, assuming an ideal Job. Defaults to AverageSetup . |
||
|
Name of the Input Resource type that is processed by the Device, (e.g., Media , Ink , RunList ). |
||
|
Unit of measure of Resource consumption per hour. Default value is from: Resource’s generic units as defined in Table 1-7, “Units used in JDF”. |
7.3.12 TestPool
The TestPool Subelement is used to contain Boolean expressions that are used to describe “templates” for use in Action Elements.
|
Test * |
A list of independent Test Elements. |
7.3.12.1 Test
The Test Subelement is used to contain Boolean expressions that are for use only when referenced by another Test or Action and are not evaluated independently. Its purpose is to simplify the description of other Test Elements and macro Elements by representing a commonly used Boolean expression.
|
Unique identifier of a Test Element. This ID is used to refer to the Test Element. |
||
|
Any Element derived from an Abstract Term , (e.g., “ not ”, “ and ” or one of the explicit Evaluation Elements). |
7.3.13 Term
Figure 7-78 shows all Term Elements
|
The Abstract Term Element serves as the basis for all constraint expressions and conditional macro expressions. It describes a (potentially) nested Boolean expression that evaluates as a whole to either "true" or "false" . This expression is then used inside constraint or macro Elements to determine proper action given the evaluation of the Term . The Term Elements are composed of Boolean combinations of Elements in Table 7-437 . The Term Elements that are Boolean operators may be nested. They are used both in Device capabilities and preflighting context.
Note: in the actual JDF schema, several Abstract Element definitions are used to create an appropriate inheritance structure. Rather than reproduce this here, only the actual non-Abstract Elements that will appear in JDF files will be described
|
Reference to a constraint Test Element to be evaluated as a nested Boolean expression inside a larger expression. |
||
|
Elements, which evaluate a JDF State Attribute Value to create a simple Boolean expression, e.g., “Is the value of BitDepth equal to 8?”. Each XXXExpression Element is derived from the Abstract Evaluation Element |
Example 7-59: ActionPool and TestPool
Term is an Abstract Element, so it will never appear in a JDF document. In this "ctcmp" constraint example, the Term is represented by the and Element. Since the Term Element itself is Abstract, what will actually appear in constraints will be Boolean expressions. In this example, the logic is, “We can not use CCITT compression if the bit depth is not 1 bit.” The check for compression type uses an EnumerationEvaluation Element, which evaluates an EnumerationState value against "CCITTFaxEncode". If the value of the EnumerationState Element referred to by "cmp" = CCITTFaxEncode , the EnumerationEvaluation evaluates as "true" . The check for "btd" is accomplished through a TestRef to the "is1bit" constraint. The and and not Elements behave according to the standard semantics for Boolean combinatorial logic.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<Device Class="Implementation" ID="Link0003" Status="Available">
< Action ID = "MyAction" TestRef = "ctcmp" >
< Loc HelpText = "Only select CCITTFaxEncoding for 1 bit documents"
Lang = "en" ShortValue = "Ouch!"
Value = "CCITTFaxEncoding not supported on
<!-- Can't CCITT compress anything but 1 bit grayscale -->
< EnumerationEvaluation ValueList = "CCITTFaxEncode" rRef = "cmp" />
< IntegerEvaluation ValueList = "1" rRef = "btd" />
<DeviceLink Usage="Input" rRef="Link0003"/>
7.3.13.1 and
The and Element evaluates two or more Term Elements to determine if, as a set, they evaluate to "true" when combined in a Boolean “and” function.
|
Any Element derived from an Abstract Term . |
||
|
Term + |
Any Element derived from an Abstract Term . |
7.3.13.2 or
The or Element evaluates two or more Term Elements to determine if, as a set, they evaluate to "true" when combined in a Boolean “or” function.
|
Any Element derived from an Abstract Term . |
||
|
Term + |
Any Element derived from an Abstract Term . |
7.3.13.3 xor
The xor Element evaluates two or more Term Elements to determine if, as a set, they evaluate to "true" when combined in a Boolean “xor” function. For more than two arguments, exactly one Term must evaluate to "true" for the xor to evaluate to "true" . Note that this is different from the mathematical behavior of “xor”.
|
Any Element derived from an Abstract Term . |
||
|
Term + |
Any Element derived from an Abstract Term . |
7.3.13.4 not
The not Subelement inverts the Boolean state of a Term .
|
Any Element derived from an Abstract Term . |
7.3.13.5 TestRef
The TestRef Element refers to another constraint that is to be evaluated as part of the parent constraint.
|
Reference to a Test to be evaluated as a nested Boolean expression inside a larger expression. |
7.3.13.6 Evaluation
Figure 7-79 shows all Evaluation Elements
|
7.3.13.6.1 Abstract Evaluation
The following table describes the common, data type-independent parameters of all Evaluation Elements.
|
When present, describes an XPath within the file where the value to be evaluated may be found. Constraint: Exactly one of Path , rRef or BasicPreflightTest must be specified. |
||
|
A reference to State , DevCap , DevCaps or Module Elements when used in the context of Device capability descriptions. Constraint: Exactly one of Path , rRef or BasicPreflightTest must be specified. Modification note: starting with JDF 1.4, DevCap and DevCaps can also be referenced and Path added to the all constraints in this table. |
||
|
Definition of the preflight basic test to which the Evaluation refers. BasicPreflightTest is only valid when Evaluation Elements are used in the context of preflighting. The Evaluation Elements in capability descriptions must reference the appropriate State Element using rRef . For details of the BasicPreflightTest , see Section 7.2.139, “PreflightParams” . Constraint: Exactly one of Path , rRef or BasicPreflightTest must be specified. |
7.3.13.6.2 Evaluation Elements
Evaluation Elements map generalized tests against a condition to form a true or false Boolean state that can be evaluated using the Boolean logic defined below.
|
Describes operations on a numerical range of integer values. |
||
|
Describes operations on a range of matrices. Generally used to define valid orientations of Component Resources. |
||
|
Describes operations on a set of four-value rectangle values. |
||
Mapping of Evaluation Element to State Element
When used in a Device capabilities context, the Evaluation Elements map to the State Elements (i.e., BooleanState , IntegerState , etc.). These Elements each declare individual JDF Attributes for a Device capabilities description. The Evaluation Elements are instances of Term Elements that compare the value of a given State Attribute against a condition to form a true or false Boolean statement. The form of the condition depends on the type of the Evaluation - State Element pairing -- different types of pairings need different condition declarations, depending on the structure of the logic and the data type of the Evaluation and State Elements.
When used in a preflighting context, Evaluation Elements map named preflight tests against a condition to form a true or false Boolean statement.
|
Describes operations on a numerical range of integer values. |
||
|
State (all) |
||
|
Describes operations on a range of matrices. Generally used to define valid orientations of Component Resources. |
||
|
Describes operations on a set of four-value rectangle values. |
||
7.3.13.6.2.1 BooleanEvaluation
The BooleanEvaluation Element declares a Boolean value for comparison in an expression to a BooleanState Element in constraints. It inherits from the Abstract Evaluation Element described above.
7.3.13.6.2.2 DateTimeEvaluation
The DateTimeEvaluation Element declares a Boolean value for comparison in an expression to a DateTimeState Element in constraints.
|
List of inclusive minimum and maximum allowed values relative to the current system time. |
||
7.3.13.6.2.3 DurationEvaluation
The DurationEvaluation Element declares a Boolean value for comparison in an expression to a DurationState Element in constraints. It inherits from the Abstract Evaluation Element described above.
7.3.13.6.2.4 EnumerationEvaluation
The EnumerationEvaluation Element declares an enumeration value for comparison in an expression to an EnumerationState Element in constraints.
7.3.13.6.2.5 IntegerEvaluation
The IntegerEvaluation Element declares an integer value for comparison in an expression to a IntegerState Element in constraints.
7.3.13.6.2.6 IsPresentEvaluation
The IsPresentEvaluation Element checks for the existence of a tag, module or feature. It inherits from the Abstract Evaluation Element described above and has no additional Attributes. IsPresentEvaluation / @rRef MAY reference a DevCap Element in order to test for the existence of an Element.
IsPresentEvaluation /@ rRef MAY reference a DevCaps Element in order to test for the existence of a Resource.
7.3.13.6.2.7 MatrixEvaluation
The MatrixEvaluation Element declares a matrix value for comparison in an expression to a MatrixState Element in constraints.
|
Allowed Modulo of the allowed rotations and offset in degrees. Note: Although this seems counter-intuitive and contrary to the convention set in JDF coordinate systems, the application of RotateMod in practice will involve subtracting values by the value of the RotateMod . Hence, any number is reduced by "0" and is unaffected by the subtraction. |
||
|
If Transforms is specified, the implied shift defined in Table 2-4, “Matrices and Orientation values for describing the orientation of a Component” is subtracted from Shift , thus all in-place rotations have an implied Shift value of "0 0 0 0" . |
||
|
The tolerance between the real and actual values that are defined as equal. Used to account for rounding errors and such. The first value is a positive value representing the negative tolerance, and the second value represents the positive tolerance. The tolerance applies to all of the matrix values. |
||
|
Any of the eight predefined transforms for Physical Resource s as defined in Table 2-4, “Matrices and Orientation values for describing the orientation of a Component”. |
||
|
Value * |
A list supported values. The Value /@ Value Attribute must be a representation of a matrix. See Section 7.3.13.6.2.7.1, “Value”. |
7.3.13.6.2.8 NameEvaluation
The NameEvaluation Element declares a NMTOKEN value for comparison in an expression to a NameState Element in constraints.
7.3.13.6.2.9 NumberEvaluation
The NumberEvaluation Element declares a number value for comparison in an expression to a NumberState Element in constraints.
7.3.13.6.2.10 PDFPathEvaluation
The PDFPathEvaluation Element declares a PDF path value for comparison in an expression to a PDFPathState Element in constraints.
|
Inclusive minimum and maximum length of valid PDF path in characters. |
||
|
Value * |
PDF path values for comparison in an expression to a PDFPathState Element. See Section 7.3.13.6.2.10.1, “Value”. |
7.3.13.6.2.11 RectangleEvaluation
The RectangleEvaluation Element declares a Boolean value for comparison in an expression to a RectangleState Element in constraints.
7.3.13.6.2.12 ShapeEvaluation
The ShapeEvaluation Element declares a shape value for comparison in an expression to a ShapeState Element in constraints.
|
The tolerance between the real and actual values that are defined as equal. Used to account for rounding errors and such. The first value is a positive value representing the negative tolerance, and the second represents the positive tolerance. The tolerance applies to all values tested. |
||
|
Allowed X-axis of the Shape . |
||
|
Allowed Y-axis of the Shape . |
||
|
Allowed Z-axis of the Shape . |
7.3.13.6.2.13 StringEvaluation
The StringEvaluation Element declares a string value for comparison in an expression to a StringState Element in constraints.
|
Inclusive minimum and maximum length of valid string in characters. Note that this is the length in characters, and not in bytes of the internal encoding of an application. For instance, the length of the string "Grün" is 4 and not 6 (UTF-8 with a terminating 0 and a double byte "ü" ). |
||
|
Value * |
A string value for comparison in an expression to a StringEvaluation Element. See Section 7.3.13.6.2.13.1, “Value”. |
7.3.13.6.2.14 XYPairEvaluation
The XYPairEvaluation Element declares a XYPair value for comparison in an expression to a XYPairState Element in constraints.
7.3.14 Examples of Device Capabilities
All of the examples in this section are based on a simple definition of a scanner. The JMF based hand shaking is also illustrated. NodeInfo , ExposedMedia and ScanParams are restricted.
7.3.14.1 Device Description of a Scanner
This first example shows the general structure and provides an example of user interface localization (the query requests localization for the French language, and localizations are returned for the ScanParams Resource).
Example 7-60: KnownDevices Query for a Scanner
< JMF xmlns = "http://www.CIP4.org/JDFSchema_1_1" MaxVersion = "1.4" Version = "1.4"
TimeStamp = "2005-04-05T16:45:43+02:00" SenderID = "Controller"
xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" >
< Query ID = "DeviceQuery" Type = "KnownDevices" xsi:type = "QueryKnownDevices" >
< DeviceFilter DeviceDetails = "Capability" Localization = "fre" />
Example 7-61: KnownDevices Response for a Scanner
< JMF xmlns = "http://www.CIP4.org/JDFSchema_1_1" SenderID = "Scanner"
TimeStamp = "2005-06-05T16:45:43+02:00" MaxVersion = "1.4" Version = "1.4"
xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" >
< Response ID = "xyz" Type = "KnownDevices" refID = "DeviceQuery"
xsi:type = "ResponseKnownDevices" >
< DeviceInfo DeviceStatus = "Idle" >
< Device Class = "Implementation" DeviceID = "Joe the Drum"
KnownLocalizations = "En Fre" ModelName = "Bongo" >
< DeviceCap GenericAttributes = "ID Class SettingsPolicy
BestEffortExceptions OperatorInterventionExceptions
MustHonorExceptions PartIDKeys DocIndex"
Lang = "Fre" Type = "Scanning" >
<!-- the scanner takes a minute to set up and scans an average
< Performance AverageAmount = "120" AverageSetup = "PT2M"
<!-- NodeInfo only supports JobPriority and
---- TargetRoute Attributes -->
< StringState Name = "TargetRoute" HasDefault = "false" />
< IntegerState Name = "JobPriority" HasDefault = "false" />
< DevCaps Name = "ExposedMedia" >
<!-- ExposedMedia restrictions -->
< NameState DefaultValue = "Sheet" Name = "MediaUnit" />
< XYPairState AllowedValueMax = "600 1200"
Name = "Dimension" HasDefault = "false" />
< DevCaps Name = "ScanParams" >
< Loc HelpText = "Les parametres pour commander le
Value = "Les parametres de module de balayage" />
<!-- Black and white 1 bit mode -->
< IntegerState AllowedValueMax = "1" AllowedValueMin = "1"
DefaultValue = "8" Name = "BitDepth" />
< EnumerationState AllowedValueList = "CCITTFaxEncode None"
Name = "CompressionFilter" HasDefault = "false" >
< Loc HelpText = "Choisissez la compression pour reduire la
Value = "La compression de donnees" />
< ValueLoc Value = "CCITTFaxEncode" >
< Loc Value = "Compression de CCITT Fax" />
< Loc Value = "Aucun compression" />
< NumberState AllowedValueMax = "10" AllowedValueMin = "1.e-002"
Name = "Magnification" HasDefault = "false" >
< Loc ShortValue = "Rapport optique"
Value = "Rapport de rapport optique d'image" />
< EnumerationState AllowedValueList = "GrayScale"
Name = "OutputColorSpace" HasDefault = "false" >
< Loc ShortValue = "Format de couleur"
Value = "Configurez le format de couleur de
< ValueLoc Value = "GrayScale" >
< Loc Value = "echelle de gris" />
< XYPairState DefaultValue = "2400 2400"
< Loc ShortValue = "resolution"
Value = "Resolution de module de balayage" />
<!-- Grayscale 12 bit mode -->
< IntegerState AllowedValueMax = "12" AllowedValueMin = "12"
DefaultValue = "8" Name = "BitDepth" >
< Loc Value = "Le profondeur de bit" />
AllowedValueList = "FlateEncode DCTEncode None"
Name = "CompressionFilter" HasDefault = "false" >
< Loc HelpText = "Choisissez la compression pour
reduire la taille de donnees."
Value = "La compression de donnees" />
< ValueLoc Value = "FlateEncode" >
< Loc Value = "Compression de Flate" />
< ValueLoc Value = "DCTEEncode" >
< Loc Value = "Compression de DCTE" />
< Loc Value = "Aucun compression" />
< NumberState AllowedValueMax = "10" AllowedValueMin = "0.001"
Name = "Magnification" DefaultValue = "1.0" >
< Loc ShortValue = "Rapport optique"
Value = "Rapport de rapport optique d'image" />
< EnumerationState AllowedValueList = "GrayScale"
Name = "OutputColorSpace" HasDefault = "false" >
< Loc ShortValue = "Format de couleur"
Value = "Configurez le format de couleur de
< ValueLoc Value = "GrayScale" >
< Loc Value = "Echelle de gris" />
< XYPairState AllowedValueMax = "2400 2400"
AllowedValueMin = "100 100" DefaultValue = "600 600"
< Loc ShortValue = "resolution"
Value = "Resolution de module de balayage" />
< IntegerState AllowedValueMax = "10" AllowedValueMin = "10"
DefaultValue = "8" Name = "BitDepth" >
< Loc Value = "Le profondeur de bit" />
AllowedValueList = "FlateEncode DCTEncode None"
< Loc HelpText = "Choisissez la compression pour reduire
Value = "La compression de donnees" />
< ValueLoc Value = "FlateEncode" >
< Loc Value = "Compression de Flate" />
< ValueLoc Value = "DCTEEncode" >
< Loc Value = "Compression de DCTE" />
< Loc Value = "Aucun compression" />
< NumberState AllowedValueMax = "10" AllowedValueMin = "1.e-002"
< Loc ShortValue = "Rapport optique"
Value = "Rapport de rapport optique d'image" />
< EnumerationState AllowedValueList = "CMYK RGB LAB"
< Loc ShortValue = "Format de couleur"
Value = "Configurez le format de couleur de
< Loc Value = "Couleur de CMYK" />
< Loc Value = "Couleur de RGB" />
< Loc Value = "Couleur de LAB" />
< XYPairState AllowedValueMax = "2400 2400"
DefaultValue = "600 600" Name = "OutputResolution" >
< Loc ShortValue = "resolution"
Value = "Resolution de module de balayage" />
7.3.14.2 Device Description of a Scanner #2
This second example illustrates the use of constraints, macros and DisplayGroup Elements in a capability response. For the sake of simplicity, the only localizations returned are for the constraints.
Example 7-62: KnownDevices Query for a Scanner #2
< JMF xmlns = "http://www.CIP4.org/JDFSchema_1_1" SenderID = "Controller"
TimeStamp = "2005-04-05T16:45:43+02:00" MaxVersion = "1.4" Version = "1.4"
xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" >
< Query ID= "DeviceQuery" Type = "KnownDevices" xsi:type = "QueryKnownDevices" >
< DeviceFilter DeviceDetails = "Capability" Localization = "en" />
Example 7-63: KnownDevices Response for a Scanner #2
< JMF SenderID = "Scanner" TimeStamp = "2004-10-17T14:30:47Z"
xmlns = "http://www.CIP4.org/JDFSchema_1_1" MaxVersion = "1.4" Version = "1.4"
DescriptiveName = "Example from JDF 1.2 Spec Document"
xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" >
< Response ID = "xyz" Type = "KnownDevices" refID = "DeviceQuery" ReturnCode = "0"
Acknowledged = "false" xsi:type = "ResponseKnownDevices" >
< DeviceInfo DeviceStatus = "Idle" >
< Device DeviceID = "Joe the Drum" ModelName = "Bongo" >
< DeviceCap GenericAttributes = "ID Class SettingsPolicy
BestEffortExceptions OperatorInterventionExceptions
MustHonorExceptions PartIDKeys DocIndex"
Type = "Scanning" CombinedMethod = "None"
ExecutionPolicy = "AllFound" >
< Performance AverageAmount = "120.0" Name = "ExposedMedia" />
< EnumerationState MinOccurs = "1"
AllowedValueList = "Mono ColorTransparency Photo"
UserDisplay = "Display" Editable = "true" ID = "sm"
ListType = "SingleValue" HasDefault = "true" Name = "ScanMode"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" MaxOccurs = "1"
MacroRefs = "ScanModeMacro" />
< DisplayGroup rRefs = "btd cmp mag colorspace outputres" >
< Loc HelpText = "Parameters for scanning configuration"
Lang = "en" ShortValue = "ScanningParameters" />
< Action Severity = "Error" TestRef = "BD-bw" ID = "BD-bw-action" >
< Loc HelpText = "For 1 bit grayscale, please select
Lang = "en" ShortValue = "Ouch!"
Value = "Flate and DCT Encoding not allowed
< Action Severity = "Error" TestRef = "ctcmp" ID = "ctcmp-action" >
< Loc HelpText = "Only select CCITTFaxEncoding for
Lang = "en" ShortValue = "Ouch!"
Value = "CCITTFaxEncoding not supported on
< Action Severity = "Error" TestRef = "cd" ID = "cd-action" >
< Loc HelpText = "Choose a bit depth of 10 or less
Lang = "en" ShortValue = "Ouch!"
Value = "Bit depths higher than 10 are not
ValueList = "RGB LAB CMYK" rRef = "colorspace" />
< IntegerEvaluation ValueList = "1" rRef = "btd" />
ValueList = "FlateEncode DCTEncode"
< EnumerationEvaluation ValueList = "CCITTFaxEncode"
< IntegerEvaluation ValueList = "1 10" rRef = "btd" />
< macro ID = "ScanModeMacro" >
< EnumerationEvaluation ValueList = "Mono" rRef = "sm" />
< FeatureAttribute CurrentValue = "1" />
< FeatureAttribute CurrentValue = "GrayScale" />
< FeatureAttribute CurrentValue = "1200 1200" />
< EnumerationEvaluation ValueList = "ColorTransparency"
< FeatureAttribute CurrentValue = "8" />
< FeatureAttribute CurrentValue = "RGB" />
< FeatureAttribute CurrentValue = "600 600" />
< EnumerationEvaluation ValueList = "Photo" rRef = "sm" />
< FeatureAttribute CurrentValue = "10" />
< FeatureAttribute CurrentValue = "LAB" />
< FeatureAttribute CurrentValue = "200 200" />
< DevCaps Required = "false" Context = "Resource"
DevNS = "http://www.CIP4.org/JDFSchema_1_1"
Name = "NodeInfo" ResourceUpdate = "None" >
< DevCap MinOccurs = "1" Name = "NodeInfo"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" MaxOccurs = "1" >
< StringState UserDisplay = "Display"
DevNS = "http://www.CIP4.org/JDFSchema_1_1"
Editable = "true" MinOccurs = "1" MaxOccurs = "1"
Name = "TargetRoute" HasDefault = "true"
< IntegerState Name = "JobPriority"
DevNS = "http://www.CIP4.org/JDFSchema_1_1"
Editable = "true" MinOccurs = "1" MaxOccurs = "1"
UserDisplay = "Display" HasDefault = "true"
< DevCaps Required = "false" ResourceUpdate = "None" Context = "Resource"
Availability = "Installed" Name = "ExposedMedia"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" >
< DevCap MinOccurs = "1" Name = "ExposedMedia"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" MaxOccurs = "1" >
< DevCap MinOccurs = "1" Name = "Media"
DevNS = "http://www.CIP4.org/JDFSchema_1_1"
< NameState MinOccurs = "1" DefaultValue = "Sheet"
UserDisplay = "Display" Editable = "true"
ListType = "SingleValue" HasDefault = "true"
Name = "MediaUnit" MaxOccurs = "1"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" />
< XYPairState MinOccurs = "1" UserDisplay = "Display"
Editable = "true" AllowedValueMax = "600.0 1200.0"
ListType = "SingleValue" HasDefault = "true"
Name = "Dimension" AllowedValueMin = "0.0 0.0"
DevNS = "http://www.CIP4.org/JDFSchema_1_1"
< DevCaps Required = "false" Context = "Resource"
DevNS = "http://www.CIP4.org/JDFSchema_1_1"
Availability = "Installed" Name = "ScanParams"
< DevCap MinOccurs = "1" Name = "ScanParams"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" MaxOccurs = "1" >
< IntegerState MinOccurs = "1" DefaultValue = "1"
AllowedValueList = "1 4 8 10 12" UserDisplay = "Hide"
ActionRefs = "BD-bw ctcmp cd" Editable = "true"
ID = "btd" ListType = "SingleValue" HasDefault = "true"
Name = "BitDepth" MaxOccurs = "1"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" />
< EnumerationState ActionRefs = "BD-bw ctcmp" MinOccurs = "1"
"CCITTFaxEncode FlateEncode DCTEncode None"
UserDisplay = "Hide" Editable = "true" ID = "cmp"
ListType = "SingleValue" HasDefault = "true"
Name = "CompressionFilter" MaxOccurs = "1"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" />
< NumberState MinOccurs = "1" UserDisplay = "Display"
Editable = "true" ID = "mag" ListType = "SingleValue"
HasDefault = "true" AllowedValueMax = "100.0"
AllowedValueMin = "0.01" MaxOccurs = "1"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" />
< EnumerationState ActionRefs = "cd" MinOccurs = "1"
AllowedValueList = "GrayScale CMYK RGB LAB"
UserDisplay = "Display" Editable = "true"
ID = "colorspace" ListType = "SingleValue"
HasDefault = "true" Name = "OutputColorSpace"
DevNS = "http://www.CIP4.org/JDFSchema_1_1" />
< XYPairState MinOccurs = "1" DefaultValue = "600.0 600.0"
AllowedValueList = "100.0 100.0 300.0 300.0 600.0 600.0
UserDisplay = "Display" Editable = "true" ID = "outputres"
ListType = "SingleValue" HasDefault = "true"
Name = "OutputResolution" MaxOccurs = "1"
Example 7-64: JDF Accepted by Previous Scanner
Example of JDF Node that is accepted by the scanner of the previous example. All parameters of the following Scanning Node are compliant with the capabilities.
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID = "GoodScan"
Status = "Waiting" Type = "Scanning" JobPartID = "ID300" Version = "1.4" >
< ScanParams BitDepth = "8" Class = "Parameter" ID = "Link0007"
OutputColorSpace = "RGB" OutputResolution = "600. 600." Status = "Available" />
< ExposedMedia Class = "Handling" ID = "Link0008" Status = "Available" >
< Media Dimension = "425.196850394 566.929133858" />
< RunList Class = "Parameter" ID = "Link0014" Status = "Available" />
< ScanParamsLink Usage = "Input" rRef = "Link0007" />
< ExposedMediaLink Usage = "Input" rRef = "Link0008" />
Example 7-65: JDF Rejected by Previous Scanner
Example of JDF Node that is rejected by the scanner of the previous example. All parameters of the following Scanning Node except Magnification are compliant with the Device capabilities. Therefore, the Device can not execute the Job.
< JDF xmlns = "http://www.CIP4.org/JDFSchema_1_1" ID = "BadScan" Status = "Waiting"
Type = "Scanning" JobPartID = "ID300" Version = "1.4" >
< ScanParams BitDepth = "8" Class = "Parameter" ID = "Link0012"
OutputColorSpace = "RGB" OutputResolution = "600. 600." Status = "Available" />
< ExposedMedia Class = "Handling" ID = "Link0013" Status = "Available" >
< Media Dimension = "425.196850394 566.929133858" />
< RunList Class = "Parameter" ID = "Link0014" Status = "Available" />
< ScanParamsLink Usage = "Input" rRef = "Link0012" />
< ExposedMediaLink Usage = "Input" rRef = "Link0013" />
7.4 Concept of the Preflight Process
Note: This section establishes Elements, Attributes and Attribute Values that are used by the Resources referenced by the Preflight Process, including PreflightParams , PreflightReportRulePool and PreflightReport , as well as extensions of testing methodology established Action and Test functions defined in Section 7.3.1, “DeviceCap” .
In order to define one Test , you can combine one or more basic tests using the Boolean logic as defined in Section 7.3, “Device Capability Definitions” . Each basic test is applied to one defined property with a given data type. Note that document properties defined in this section include one or more Attributes that are extracted from documents (e.g., a client’s PDF file) and used by one or more evaluations as part of a preflight test. Each data type can be tested on an object using its matching Evaluation . A document that is preflighted is made of objects. Some of them, like virtual boxes ( TrimBox or MediaBox ) are not visible. In order to combine basic tests together, they have been classified by groups of properties. These groups do not necessarily match a class of an object. However, each class of object will implement one ore more groups of properties.
The rules to combine basic tests into a Test can be built on both object classes and groups of properties. Each basic test takes an object as an input and has four different states in output: "false" , "true" , "TestWrongPDL" or "TestNotSupported" . The two last values occur when a basic test has no meaning for the given object or when the application that is executing the test does not support that test. These four different states lead to a more open way of dealing with Boolean logic
|
Report problem if specified in PRRule . |
||||
|
Report problem if specified in PRRule . |
||||
For instance, "TestWrongPDL" would occur when a test about font size is made on a page. "TestNotSupported" would happen when a JDF preflight agent does not support the concept of font size.
7.4.1 Object Classes
Table 7-463, “Object Classes for a Document” below has a list of the real objects that can be preflighted in a document. The objects are identified by their class name specified in the “Name” column:
7.4.1.1 Properties Implemented by each Class of Object
Table 7-464, “Properties Implemented by each Class of Object” below, has columns of object Classes and rows of Properties Categories. An “X” in a cell means that an object of the specified Class implements the specified Properties (see Table 7-466, “List of Properties Categories”).
7.4.1.2 Checking for the Presence of a Property
In most of the Preflight Process, only the “values” of properties are needed. Please note that a property may incorporate one or more Attributes, and it is the values (e.g., string or enumeration) of these Attributes that are collectively referred to here as the “value” of the property. In some cases, it is also useful to be able to check if a property has been defined. This happens in some types of documents where the property definition is optional. Before checking its value, you just want to check that this property was defined.
For all the basic tests described in this document where it makes sense to check if they are defined, they are checked “Yes” in the Tag column of properties definition tables below. Use the IsPresentEvaluation to check for the presence of a property.
Example 7-66: Test for Existence of TrappedKey
This example checks if the TrappedKey is defined in a PDF document.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<Device Class="Implementation" ID="Link0003" Status="Available">
< BasicPreflightTest Name = "TrappedKey" />
Example 7-67: Test for TrappedKey Equal to “Unknown”
This example checks if the value of the TrappedKey = "Unknown" in a PDF document.
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<Device Class="Implementation" ID="Link0003" Status="Available">
< EnumerationEvaluation ValueList = "Unknown" >
< BasicPreflightTest Name = "TrappedKey" />
<DeviceLink Usage="Input" rRef="Link0003"/>
7.4.1.3 Basic tests on set of objects
Some properties can be applied to more than one object and have a value when applied to a list of objects which differs from their value when applied to a single object. For instance, this allows you to make tests on the number of separations of objects included in a given area. These properties have the column “Set” checked with "Yes" . In order to define a Test using such properties, a list of objects is filtered first, before applying the test. This is achieved using the PreflightArgument Element.
7.4.2 Properties
Table 7-466, “List of Properties Categories”specifies the Properties Categories. In each of the following subsections, there is a table with a list of Attributes belonging to the specified Properties Category. Each such Attribute can be found, extracted, and evaluated from a document. The Attributes of each Properties Category apply to Objects of certain specified Classes (see Table 7-465, “Mapping between property types (in the preflight spec) and evaluations”).
Note: each table of Properties in the subsections below has a different meaning from a table for an Element or Resource, which describes an XML element along with its member attributes or subelements. A Properties table does not describe an XML element or any other structure. Rather each table row describes an Attribute that is a potential Attribute of some Element derived from Abstract PRGroupOccurrenceBase Element (see Table 7-303, “List of PRGroupOccurrenceBase Elements”).
Note also: for each Properties tables, the “Set” column is described in Section 7.4.1.3, “Basic tests on set of objects”, and the “Tag” column is described in Section 7.4.1.2, “Checking for the Presence of a Property”.
|
Describes strokes applied to graphic objects with vector primitives |
||
7.4.2.1 Annotation Properties
Annotation objects are specific objects that can be displayed or printed according to the user’s choice. When they are displayed or printed, they add graphical objects to the document that can be preflighted.
|
Values include those from: Table 7-468, “AnnotationType Attribute Values”. |
|||||
|
The PDF/X versions to which the TrapNet annotation complies, (e.g., "PDF/X- 1a:2003 " ). |
7.4.2.2 Box Properties
All visible objects can be described at least by a box in which they can be contained. In a page, some kind of boxes can define some basic Box Properties that are extracted as Attributes for use in a test.
|
The bounding box of the object is the smallest rectangle containing the object. When used with group of objects, this is the smallest box containing boxes of all objects. |
|||||
|
This is the list of boxes, which are different on one page from the same boxes on another page. Values are from: BoxArgument /@ Box (Table 7-295, “BoxArgument Element”). |
|||||
|
Is "true" when an object is inside a given box. InsideBox must be qualified by BoxArgument Subelement. |
|||||
|
Is "true" when an object is outside a given box. OutsideBox must be qualified by BoxArgument Subelement. |
7.4.2.3 Class Properties
Each object can define the name of the class of objects it belongs to:
|
The name of the class to which the object belongs. Values include those from: Table 7-471, “ClassName Attribute Values”. |
|||||
|
The list of Properties the object has. Values are from: Table 7-472, “PropertyList Attribute Values”. |
7.4.2.4 Colorant Properties
Every visible object or group of objects will imply a given number of separations.
7.4.2.5 Document Properties
This is the list of Properties (Attributes) that define parts of a document.
|
The date when the document was created according to the file system. |
|||||
|
The date when the document was created according to data inside the document. |
|||||
|
An NMTOKEN which can uniquely identify a document when created. In case of a PDF, it matches exactly the first element of ID array. |
|||||
|
A string describing the creator of the document. This is usually the name and version of the authoring application used. In case of PS and PDF files, it matches exactly the Creator key. |
|||||
|
A list of all compression types used in the document (including image compression referenced by CompressionTypes in Image Properties ). Values are from: @ CompressionTypes in Table 7-480, “Image Properties”. |
|||||
|
The list of recoverable errors against the document format that were found in this document. An empty list means the document is not corrupted. InvalidOffsets - Some offsets are invalid, but the preflight agent was able to load the document nonetheless. Note that the absence of this value does not mean that all document structures are valid, only that the offsets are correct) |
|||||
|
Is "true" when a strong compression algorithm is used (not just an ASCII filter) for all objects in the document where it makes sense to have compression. |
|||||
|
The actions that are forbidden by the encryption. Assembly - Inserting or removing pages. Copying - Extracting part of the content. DisabledAccess - Allowing copying specifically for providing access to the disabled. |
|||||
|
The file name, including file extension, in the file system. This is not the full path. |
|||||
|
Is "true" if the document is linearized, (i.e., prepared for web download). |
|||||
|
The date when the document was last modified according to the file system. |
|||||
|
The date when the document was last modified according to data inside the document. |
|||||
|
A name that which can uniquely identify the current document instance. In case of a PDF, it matches exactly the second element of ID array. |
|||||
|
The color space belonging to the output intent of the document. None - The default value to be used if this property is not present. |
|||||
|
The standards the output intent is compliant with, (e.g., PDF/X- 1a:2001 ). The version of the standard is assumed to be in the string accordingly to the standard’s notation. |
|||||
|
The type of document expressed as a MIME-type. Values include those from: Table H-1, “MimeType Attribute Values (IANA Registered)” and Table H-2, “MimeType and File Type Combinations”. |
|||||
|
The version of document according to the PDLType . Values include those from: Table H-1, “MimeType Attribute Values (IANA Registered)” and Table H-2, “MimeType and File Type Combinations”. |
|||||
|
A string describing the producer of the document. This is usually the name of the software used to create file. In case of PDF files, it matches exactly the Producer key. |
|||||
|
Is "true" if the document is made of separations or is not composite. |
|||||
|
A value explaining the use of trapping on the document. Note: the values match exactly the TrappedKey information of PDF. |
7.4.2.6 Fill Properties
Fill property values are derived from graphic objects with vector primitives. They can have a fill color and a stroke color, with given colors. This is a list of Properties that specifically apply to this kind of object:
|
This is an enumeration of known colors to draw fill. Values are from: Table 7-476, “FillColorType Attribute Values”. |
|||||
-- Attribute: FillColorType
7.4.2.7 Font Properties
The following is the list of property Attributes that can be applied to a font contained in, or referenced into, a document:
|
Is "true" if a font is corrupted or invalid. The implementation of this check may vary from one application to another. |
|||||
|
Is "true" when all characters belong to the standard Latin character set. |
|||||
|
Is "true" if a font is not used to draw characters from the document. |
|||||
|
FontType = "Other" |
Values are from: Table 7-478, “FontType Attribute Values”. |
||||
|
Some fonts need double-byte encoding to store characters internally |
|||||
|
Is "true" if a font referenced in the document contains only screen description. |
|||||
-- Attribute: FontType
|
Type of font that can not be resolved for any reason, (i.e., missing font, etc.). |
||||
|
To be used when the property is not any of the values listed above. |
7.4.2.8 Graphic Properties
This is a list of property Attributes that specifically apply to objects that can be displayed or printed.
7.4.2.9 Image Properties
This group of property Attributes is very specific to images displayed using pixels:
The JPEG quality algorithm is based on a technique used by the IJG library ( http://www.ijg.org/ ) -- which uses a quality value in the range 0-100 and translates image data into a 8x8 matrix. The following algorithm performs a “reverse statistic” on the IJG library’s quality-to-matrix routine, which gives a matrix-to-quality routine. The formula’s used are as follows:
//DCTSIZE2 is the size of the matrix, 64
derived = 0.0;
for (i = 0; i < DCTSIZE2; i++){
derived += (*qtblptr0)->quantval[i];
xq = (100.0 * derived - 50.0) / 57.625;
quality = (long) ((200.0 - xq) / 2.0);
quality = (long) (5000.0 / xq);
The algorithm calculates the average value in the quantization matrix and then derives a quality value in the range of 0-100 from that average.
7.4.2.10 Logical Properties
The logical Properties are mainly used with “ Set ” to count the number of objects.
|
The number of objects contained in the referenced set of objects. |
7.4.2.11 PageBox Properties
The page box represents virtual boxes for each page. The following is a list of Attributes that specifically apply to this kind of objects.
|
Note: when not known, the default is to leave PageBoxType empty. Values are from: BoxArgument /@ Box (Table 7-295, “BoxArgument Element”). |
7.4.2.12 Pages Properties
This is the list of Elements and Attributes related to the page object in a document.
|
Is "true" when the trim box and the bleed box area, when defined, do not output any marks. |
|||||
|
Values are from : @ ColorSpace in Table 7-479, “Graphic Properties”. |
|||||
|
Detect if a PDF has optional content (commonly called PDF layers). |
|||||
|
Page contains unknown objects but the PDL was set to ignore these errors. Examples are the use of BX/EX in PDF. |
|||||
|
The page index in the RunList . |
|||||
|
In PDF file, one way of scaling a page is to use a page scale factor. This factor can be ambiguous because it is not always used by all applications. |
|||||
|
A special page numbering which starts from the last page. The last page is "-1" . This has been added to allow filtering of last page or the before last page, which is "-2" . It is used to apply specific test on a document cover. |
|||||
|
The rectangle from calculating the differences between two rectangles: FromBox and ToBox . The calculation is made using the following formula: FromBox (left)- ToBox (left), FromBox (bottom)- ToBox (bottom), ToBox (right)- FromBox (right), ToBox (top)- FromBox (top). To define the two boxes used, options are given in BoxToBoxDifference argument. See Table 7-297, “BoxToBoxDifference Element”. |
Note that BoxToBoxDifference Element is always a Subelement of a PreflightArgument .
Example 7-68: Test with BoxToBoxDifference Element
<JDF xmlns="http://www.CIP4.org/JDFSchema_1_1" ID="A1" Status="Waiting"
Type="ProcessGroup" JobPartID="ID300" Version="1.4">
<Device Class="Implementation" ID="Link0003" Status="Available">
< RectangleEvaluation ValueList = "0 0 10 10" >
< BasicPreflightTest Name = "BoxToBoxDifference" >
< BoxToBoxDifference FromBox = "TrimBox"
<DeviceLink Usage="Input" rRef="Link0003"/>
7.4.2.13 PDLObject Properties
The PDL object is used to check whether select objects are defined or not defined in the document, but does not check anything else as these objects are specific to one given PDL.
|
The type of specific PDL object. Bookmarks - The PDF Bookmarks. |
7.4.2.14 Reference Properties
Reference property Attributes describe objects that have links to external references on other objects. It only deals with OPI links and references in page to other graphical contents. This is not describing the Font Properties (see Section 7.4.2.7, “Font Properties” ).
7.4.2.15 Shading Properties
Shading property Attributes are derived from graphic objects with applied shading, which is usually defined as of either smooth or vector type.
7.4.2.16 Stroke Properties
Stroke property Attributes are linked with graphic objects with vector primitives. They can have a fill color and a stroke color with given colors. This is a list of Properties that specifically apply to this kind of object:
|
Is "true" if the vector object is drawn with a stroke color. |
|||||
|
The alternate color space of the stroke of one object. Values are from : @ ColorSpace in Table 7-479, “Graphic Properties”. |
|||||
|
The color space of the stroke of one object. Values are from : @ ColorSpace in Table 7-479, “Graphic Properties”. |
|||||
|
This is an enumeration of known colors used to draw stroke. Values are from : @ FillColorType in Table 7-475, “Fill Properties”. |
|||||
|
Is "true" when the stroke of one object has been set to overprint. |
|||||
7.4.2.17 Text Properties
“Text” refers to a consecutive set of one or more characters that share the same style (i.e., font, size, fill, stroke, etc.). The following are the Attributes that can be applied to text: